Re: [expert] kcontrol STILL doesn't function
no-way man! My install works great (so far). I did have one problem, but I was installing on top of the old. I deleted the .kde directories, and all the kde-related directories in /usr/share, and all the /tmp files related to kde, then followed the instructions "DO_NOT_READ_THIS" and it worked fine. Thanks, and don't quit. > > In retrospect I should never have asked for and encouraged the > unsupported > > directory, as I think it is causing more problems than it is worth. __ Do You Yahoo!? Yahoo! Auctions - Buy the things you want at great prices. http://auctions.yahoo.com/
Re: [expert] kcontrol STILL doesn't function
On Monday 05 February 2001 02:46, Christopher Molnar wrote: > > In retrospect I should never have asked for and encouraged the unsupported > directory, as I think it is causing more problems than it is worth. > Please don't get discouraged. I really appreciate the unsupported RPMs and feel that they are well worth the effort to download. While I generally don't follow the instructions to the letter I, fortunately, don't end up with a mess that some of the list members seem to have. Keep up the good work. -- Regards, Phil [EMAIL PROTECTED]
Re: [expert] kcontrol STILL doesn't function
See my nexty message. I think your problem is in QTDIR not being set. It's needed to compile kde apps. Did you keep your old home dir, or totally reformat your system? Anyways, see if this helps. -Chris
Re: [expert] kcontrol STILL doesn't function
On Sunday 04 February 2001 12:51, Christopher Molnar wrote: > First, appologies to al, because I am leaving the origional message and > just putting my comments into it. Praedor, please look for my notes all > the way to the bottom. I just thought of something. [...] > > As for my system. It is NOT a pure 7.2 system, but it has not a single > > cooker package on it and not a single beta set of packages on it EXCEPT > > for kde2.1. XFree86 is the standard, stable, latest version built from > > src.rpm. The kernel is not a bizarro kernel of my own creation, it is a > > stable Mandrake 2.2.17 kernel. My glibc is the latest Mandrake-supported > > version brought on my MandrakeUpdate for 7.2. Nothing at the heart of my > > system is beta or Cooker (or Rawhide for that matter). > > Hey, when you where doing your update cd, did you have any problems? Any > error messages? Please think carefully, did anything strange happen. I also > should have asked, did you install your origional 7.2 with Expert, novice, > or Custom and is it a Workstation, Developer, or Server install. > > Also, where did you buy the boxed set? OK, this may be a source of problem... I had Mandrake 7.1. An IT guy at my university had Mandrake 7.2 (I don't know where he got it - a software store or off the net) and he burned me copies of the two CDs. I installed from that on both my laptop and desktop. On both I did an Expert install of a developer type. On my desktop, harddrive space is not an issue so I installed EVERYTHING vis a vis development libs. On the laptop, same thing but space is a premium so I only installed the minimum devel libs and tools that I thought I could conceivably use. I honestly do not recall experiencing any problems or glitches during the installs. After installing I did the MandrakeUpdate thing. I did it again just a couple days ago to bring glibc2.1 up to the latest update versions. XFree86-4.0.2 was downloaded as source and built myself and works fine. -- Against stupidity, the gods themselves contend in vain.
Re: [expert] kcontrol STILL doesn't function
First, appologies to al, because I am leaving the origional message and just putting my comments into it. Praedor, please look for my notes all the way to the bottom. I just thought of something. On Sunday 04 February 2001 13:39, you wrote: > I will (somewhat) apologize for my previous tone and chalk it up to a set > of bad days above and beyond kcontrol problems. From here: > > On Sunday 04 February 2001 09:46, Christopher Molnar wrote: > > #1 - the unsupported are not built with cooker. I am starting to suspect > > this is the problem with a lot of the problems. They are also not built > > for cooker. > > Are you saying that the packages you are producing (I am not > unappreciative, really) should be built with cooker? Do you mean they have > cooker-specific dependencies? If so, the ONLY problem I have seen of any > real consequence is the kcontrol problem. NO!! It doesn't matter what they are built on, but what they are built on must = what they are installed on. Don't mix cooker with 7.2. > > > #2 - people do not follow directions. Every person who has followed the > > directions step by step, not tried to rebuild part of the systems, move > > menus, etc has not had any problems. There are also a lot of people who > > are mixing Cooker and 7.2 still, after repeated explanations. > > I have not mixed Cooker with 7.2. I install no rpms from cooker (most of > which would be impossible due to the glibc differences). I did nothing > (absolutely nothing) with my menus. Really. No menudrake stuff. > > You also indicated in a previous post that if we have done anything to, or > added anything to our .kde/share/applnk directory, that would be trouble. > I did not do this. Besides that, would not totally deleting .kde/ from > one's home directory, which means EVERYTHING within it including > share/applnk/ and any user-created additions within it, and then restarting > and allowing kde to setup one's home with the default settings/setup that > it always installs upon running kde for the first time, correct the > problem? I also did nothing to /usr/share/applnk or anything within it. > Running kbuildsycoca made the problem worse for me rather than correcting > it. Have you sen the descriptiions of the bugs to [EMAIL PROTECTED] or entered a bug at http://bugs.kde.org? What you describing goes way past a packaging bug and goes to a coding issue. Please let the kde team know about it. > > > #3 - you say there is not any real difference between the Unsupported and > > the cooker version, actually there is. First, I do not build the > > unsupported version on Mandrake machines. I build on a personal laptop, > > wherever in the world I happen to be traveling. For example, today I am > > Berkeley, CA. This means that Mandrake does not know what is on my > > machine so they can not support the RPMs. > > What linux version do you run on your laptop then, if not Mandrake? I was > assuming it would be one of the Mandrakes. If it isn't, then what packages > do you have installed that specifically concern building kde source? Also, > are you creating mdk rpms de novo from tarballs or are you using src.rpms? I run a pure Mandrake 7.2 install. But it is not controlled by Mandrake. I make it a personal thing to make it stay clean, but others may not be as "anal" about this as I am. > > > Further, I have removed a LARGE number of patches and am using way more > > current CVS code for all of my RPM's than you will find in cooker. It is > > not the same SRPM that has been rebuilt. I check out changes as the build > > script runs. > > OK. > > > You mention attitude and tone. I am not paid to make these RPM's, I am > > not paid to consistantly fix peoples broken systems. I think you would > > probably get a little tired of 100 emails saying that I caused their > > systems to die after I have seen a lot of other people install by > > following the directions, which most people never read. > > As I have mentioned. I did none of the things that were suggested as > causes for the kcontrol problem (menudrake, changes to my applnk > directory). I also tried the suggested fixes: copy /usr/share/applnk to > my .kde/share/applnk. In addition, I was upgrading from kde 2.1 to 2.1, not > from 2.0 to 2.1. There was a definite, if subtle, change in the whole > thing somewhere between 0112 and 0118 that resulted in this problem. All > was well with kcontrol (there were other problems like sigsevs, etc, in > other apps which is what drove the desire to upgrade to the next release of > the 2.1 beta - because these problems were fixed). Beyond that, it isn't > kde exactly, but I was also hoping to find a functional version of kword, > which gets built off each subsequent change in qt2 and kde. Alas, I have > given up on kword for now and have gone with lyx (klyx is really broken). > As nice as kword COULD be, it is merely another version of a standard linux > wordprocessor that has no bibliography/citation capabil
Re: [expert] kcontrol STILL doesn't function
Well said Chris. I'm with you 100%. Keep the faith...you're doing a great job. Since following your directions to the letter I no longer have any troubles with my machine and I thank you. -- Mark "If you don't share your concepts and ideals, they end up being worthless," "Sharing is what makes them powerful." On Sun, 4 Feb 2001, Christopher Molnar wrote: > Date: Sun, 4 Feb 2001 11:46:18 -0500 > From: Christopher Molnar <[EMAIL PROTECTED]> > Reply-To: [EMAIL PROTECTED] > To: [EMAIL PROTECTED] > Subject: Re: [expert] kcontrol STILL doesn't function > > #1 - the unsupported are not built with cooker. I am starting to suspect this > is the problem with a lot of the problems. They are also not built for cooker. > > #2 - people do not follow directions. Every person who has followed the > directions step by step, not tried to rebuild part of the systems, move > menus, etc has not had any problems. There are also a lot of people who are > mixing Cooker and 7.2 still, after repeated explanations. > > #3 - you say there is not any real difference between the Unsupported and the > cooker version, actually there is. First, I do not build the unsupported > version on Mandrake machines. I build on a personal laptop, wherever in the > world I happen to be traveling. For example, today I am Berkeley, CA. This > means that Mandrake does not know what is on my machine so they can not > support the RPMs. > > Further, I have removed a LARGE number of patches and am using way more > current CVS code for all of my RPM's than you will find in cooker. It is not > the same SRPM that has been rebuilt. I check out changes as the build script > runs. > > I do not advise going to the new glibc, I differ in the opinion of my > employers with this (ok, I am now going to get shot) I think that the > developers of gcc have a reason for advising us not to use the latest > development version in a distro. The KDE team has said NOT to use the new > version to compile kde in a distro, again so I do not. > > You mention attitude and tone. I am not paid to make these RPM's, I am not > paid to consistantly fix peoples broken systems. I think you would probably > get a little tired of 100 emails saying that I caused their systems to die > after I have seen a lot of other people install by following the directions, > which most people never read. > > In retrospect I should never have asked for and encouraged the unsupported > directory, as I think it is causing more problems than it is worth. > > -Chris > > On Sunday 04 February 2001 11:21, you wrote: > > "They" full well know what unsupported means. It is OFFICIALLY not > > supported. Why? Is it because there is any REAL difference between the > > SUPPORTED version (in OFFICIAL cooker) and the "unsupported" versions for > > 7.2? NO. No difference. The only real difference is the former is built > > from glibc2.2 while the latter is built with glibc2.1. Big deal. > > > > For all PRACTICAL purposes, they are identical. This is proven true by the > > fact that if you download the straight source from KDE rather than from > > Mandrake sources, it does not say you MUST use glibc2.2. Many other > > distros that are making use of the latest KDE are NOT using glibc2.2 (yet). > > > > Get off your snide, sarcastic platform. Complaint or criticism IS valid, > > regardless. How would you EVER know of any problem if no one did this? As > > for tone, when repeated and repeated questions or posts of problems > > concerning what should be a VERY simple problem and answer go unanswered > > repeatedly, then I would say tone has every right to change. > > > > Get over it. > > > > On Sunday 04 February 2001 05:41, Mark Weaver wrote: > > > Chris, > > > > > > Maybe you should change the name of "unsupported" to "bleeding-edge". > > > They might get the idea then, do ya think? :) > >
Re: [expert] kcontrol STILL doesn't function
I will (somewhat) apologize for my previous tone and chalk it up to a set of bad days above and beyond kcontrol problems. From here: On Sunday 04 February 2001 09:46, Christopher Molnar wrote: > #1 - the unsupported are not built with cooker. I am starting to suspect > this is the problem with a lot of the problems. They are also not built for > cooker. Are you saying that the packages you are producing (I am not unappreciative, really) should be built with cooker? Do you mean they have cooker-specific dependencies? If so, the ONLY problem I have seen of any real consequence is the kcontrol problem. > #2 - people do not follow directions. Every person who has followed the > directions step by step, not tried to rebuild part of the systems, move > menus, etc has not had any problems. There are also a lot of people who are > mixing Cooker and 7.2 still, after repeated explanations. I have not mixed Cooker with 7.2. I install no rpms from cooker (most of which would be impossible due to the glibc differences). I did nothing (absolutely nothing) with my menus. Really. No menudrake stuff. You also indicated in a previous post that if we have done anything to, or added anything to our .kde/share/applnk directory, that would be trouble. I did not do this. Besides that, would not totally deleting .kde/ from one's home directory, which means EVERYTHING within it including share/applnk/ and any user-created additions within it, and then restarting and allowing kde to setup one's home with the default settings/setup that it always installs upon running kde for the first time, correct the problem? I also did nothing to /usr/share/applnk or anything within it. Running kbuildsycoca made the problem worse for me rather than correcting it. > > #3 - you say there is not any real difference between the Unsupported and > the cooker version, actually there is. First, I do not build the > unsupported version on Mandrake machines. I build on a personal laptop, > wherever in the world I happen to be traveling. For example, today I am > Berkeley, CA. This means that Mandrake does not know what is on my machine > so they can not support the RPMs. What linux version do you run on your laptop then, if not Mandrake? I was assuming it would be one of the Mandrakes. If it isn't, then what packages do you have installed that specifically concern building kde source? Also, are you creating mdk rpms de novo from tarballs or are you using src.rpms? > Further, I have removed a LARGE number of patches and am using way more > current CVS code for all of my RPM's than you will find in cooker. It is > not the same SRPM that has been rebuilt. I check out changes as the build > script runs. OK. > You mention attitude and tone. I am not paid to make these RPM's, I am not > paid to consistantly fix peoples broken systems. I think you would probably > get a little tired of 100 emails saying that I caused their systems to die > after I have seen a lot of other people install by following the > directions, which most people never read. As I have mentioned. I did none of the things that were suggested as causes for the kcontrol problem (menudrake, changes to my applnk directory). I also tried the suggested fixes: copy /usr/share/applnk to my .kde/share/applnk. In addition, I was upgrading from kde 2.1 to 2.1, not from 2.0 to 2.1. There was a definite, if subtle, change in the whole thing somewhere between 0112 and 0118 that resulted in this problem. All was well with kcontrol (there were other problems like sigsevs, etc, in other apps which is what drove the desire to upgrade to the next release of the 2.1 beta - because these problems were fixed). Beyond that, it isn't kde exactly, but I was also hoping to find a functional version of kword, which gets built off each subsequent change in qt2 and kde. Alas, I have given up on kword for now and have gone with lyx (klyx is really broken). As nice as kword COULD be, it is merely another version of a standard linux wordprocessor that has no bibliography/citation capability. Only lyx offers this ability via bibtex, pybliographic (or sixpack). This is neither here nor there. I was upgrading to fix broken things in previous versions. As everything did become more stable, kcontrol somewhere went goofy. I even uninstalled everything kde and qt on my system and reinstalled the latest kde2.1 "clean" (I was previously put off by suggestions that a total reinstall of 7.2 was in order - NO WAY). Someone finally suggested just a "clean" install of kde2.1 (thus I removed all kde stuff). Nonetheless (and again following the install order/proceedure in the README), kcontrol worked for a single session after the initial install and then went blank again - and I had done literally nothing. I then got it working again after deleting .kderc, .kde/, and everything in tmp/ and /tmp (EVERYTHING). I restarted X and kcontrol was working agai
Re: [expert] kcontrol STILL doesn't function
On Sunday 04 February 2001 08:46, Christopher Molnar wrote: > You mention attitude and tone. I am not paid to make these RPM's, I am not > paid to consistantly fix peoples broken systems. I think you would probably > get a little tired of 100 emails saying that I caused their systems to die > after I have seen a lot of other people install by following the > directions, which most people never read. > In retrospect I should never have asked for and encouraged the unsupported > directory, as I think it is causing more problems than it is worth. I'm amazed at how far KDE 2 has come since the release version of 7.2. Considering 2.0 was a milestone, I was kinda expecting the developers to take a break -- but they're obviously not. I really appreciate the work you've done to provide us with these packages, Chris, and I'm sure most who've tried them would agree. I hope you won't let one person's remarks convince you otherwise. M. -- Michael O'Henly TENZO Design
Re: [expert] kcontrol STILL doesn't function
> I do not advise going to the new glibc, I differ in the opinion of my > employers with this (ok, I am now going to get shot) I think that the > developers of gcc have a reason for advising us not to use the latest Please convince your employers that you are right (grin). I like Mandrake but their 'bleeding edge' approach seems very inconsistent with the time they're spending courting Windows desktop users with all the GUI admin tool development. Cheers --- Larry
Re: [expert] kcontrol STILL doesn't function
#1 - the unsupported are not built with cooker. I am starting to suspect this is the problem with a lot of the problems. They are also not built for cooker. #2 - people do not follow directions. Every person who has followed the directions step by step, not tried to rebuild part of the systems, move menus, etc has not had any problems. There are also a lot of people who are mixing Cooker and 7.2 still, after repeated explanations. #3 - you say there is not any real difference between the Unsupported and the cooker version, actually there is. First, I do not build the unsupported version on Mandrake machines. I build on a personal laptop, wherever in the world I happen to be traveling. For example, today I am Berkeley, CA. This means that Mandrake does not know what is on my machine so they can not support the RPMs. Further, I have removed a LARGE number of patches and am using way more current CVS code for all of my RPM's than you will find in cooker. It is not the same SRPM that has been rebuilt. I check out changes as the build script runs. I do not advise going to the new glibc, I differ in the opinion of my employers with this (ok, I am now going to get shot) I think that the developers of gcc have a reason for advising us not to use the latest development version in a distro. The KDE team has said NOT to use the new version to compile kde in a distro, again so I do not. You mention attitude and tone. I am not paid to make these RPM's, I am not paid to consistantly fix peoples broken systems. I think you would probably get a little tired of 100 emails saying that I caused their systems to die after I have seen a lot of other people install by following the directions, which most people never read. In retrospect I should never have asked for and encouraged the unsupported directory, as I think it is causing more problems than it is worth. -Chris On Sunday 04 February 2001 11:21, you wrote: > "They" full well know what unsupported means. It is OFFICIALLY not > supported. Why? Is it because there is any REAL difference between the > SUPPORTED version (in OFFICIAL cooker) and the "unsupported" versions for > 7.2? NO. No difference. The only real difference is the former is built > from glibc2.2 while the latter is built with glibc2.1. Big deal. > > For all PRACTICAL purposes, they are identical. This is proven true by the > fact that if you download the straight source from KDE rather than from > Mandrake sources, it does not say you MUST use glibc2.2. Many other > distros that are making use of the latest KDE are NOT using glibc2.2 (yet). > > Get off your snide, sarcastic platform. Complaint or criticism IS valid, > regardless. How would you EVER know of any problem if no one did this? As > for tone, when repeated and repeated questions or posts of problems > concerning what should be a VERY simple problem and answer go unanswered > repeatedly, then I would say tone has every right to change. > > Get over it. > > On Sunday 04 February 2001 05:41, Mark Weaver wrote: > > Chris, > > > > Maybe you should change the name of "unsupported" to "bleeding-edge". > > They might get the idea then, do ya think? :)
Re: [expert] kcontrol STILL doesn't function
"They" full well know what unsupported means. It is OFFICIALLY not supported. Why? Is it because there is any REAL difference between the SUPPORTED version (in OFFICIAL cooker) and the "unsupported" versions for 7.2? NO. No difference. The only real difference is the former is built from glibc2.2 while the latter is built with glibc2.1. Big deal. For all PRACTICAL purposes, they are identical. This is proven true by the fact that if you download the straight source from KDE rather than from Mandrake sources, it does not say you MUST use glibc2.2. Many other distros that are making use of the latest KDE are NOT using glibc2.2 (yet). Get off your snide, sarcastic platform. Complaint or criticism IS valid, regardless. How would you EVER know of any problem if no one did this? As for tone, when repeated and repeated questions or posts of problems concerning what should be a VERY simple problem and answer go unanswered repeatedly, then I would say tone has every right to change. Get over it. On Sunday 04 February 2001 05:41, Mark Weaver wrote: > Chris, > > Maybe you should change the name of "unsupported" to "bleeding-edge". They > might get the idea then, do ya think? :) -- Against stupidity, the gods themselves contend in vain.
Re: [expert] kcontrol STILL doesn't function
Chris, Maybe you should change the name of "unsupported" to "bleeding-edge". They might get the idea then, do ya think? :) -- Mark "If you don't share your concepts and ideals, they end up being worthless," "Sharing is what makes them powerful." On Sat, 3 Feb 2001, Christopher Molnar wrote: > Date: Sat, 3 Feb 2001 21:04:08 -0500 > From: Christopher Molnar <[EMAIL PROTECTED]> > Reply-To: [EMAIL PROTECTED] > To: [EMAIL PROTECTED] > Subject: Re: [expert] kcontrol STILL doesn't function > > On Friday 02 February 2001 14:59, you wrote: > > > Maybe you don't need to do a clean install. Maybe only KDE, CUPS, xinitrc, > > egcs, ghostscript, arts, jkd, etc. need to be updated. If you know what > > you're doing, then go for it. But to blame Mandrake because your patchwork > > upgrade breaks a beta version of KDE is just dumb. If you're not prepared > > for problems, don't run beta software. > > > > Hmmm... add to that Beta software downloaded from a directory named > "unsupported" with a README that tells you it is unsupported :-) > > Also, try sending a note to the packager, he may be willing to help you after > he reads the other 200 emails in his inbox. > > -Chris > > >
Re: [expert] kcontrol STILL doesn't function - DONE/FIXED
Please post the output of the following commands - do not send to me direct as others can probably help as well: rpm -qa|grep kde rpm -qa|grep koffice rpm -qa|grep xinitrc rpm -qa|grep qt Also an ls -l of all the rpm's you downloaded to isntall. Read on On Friday 02 February 2001 15:59, Praedor Tempus 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. the kbuildsycoca was the correct answer. However if you have any applnk contents under /home/user/.kde/share/applnk you are sometimes asking for trouble. > > 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. Someone else told you that if you do not want to take the risks do not run beta code, and I agree with that statement. However, there is no single file that provides the info to kcontrol. When the menus are built from the files in /usr/lib/menus there is a menu system built in /usr/share/applnk and under that is Configuration/KDE and in that directory is a .directory file that tells that this is where kcontrol is built from. However, if you alter that file for some reason, or it gets corrupt this will cause you problems. All you need to do at that point is run update-menus as root, wait a few moments, restart KDE and you should be set, provided you have the right packages. > > 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. No, you can't. The code is in a state of change and the files used to create the menu entries are consistantly changing. This is a risk with code in active development. You wouold need to know which one of 500 files is messing things up. > > 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. You are welcome for the termendous hours I put in building you packages. Do you know what the following words mean: Beta - unstable test release of an updated development package. Bug fixing is going on. Unsupported - means the distributitor supplies no support, you are on your own. And if you ask for support you better be nice our you will be ignored. README - The file placed in every directory, that says all of the above that people should read, but never do. DON_T_READ_THIS - the file that was put into the same directory with the hopes that since no-one ever reads the README they may read a file that say's DON't READ THIS! > > 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.
Re: [expert] kcontrol STILL doesn't function
On Friday 02 February 2001 14:59, you wrote: > Maybe you don't need to do a clean install. Maybe only KDE, CUPS, xinitrc, > egcs, ghostscript, arts, jkd, etc. need to be updated. If you know what > you're doing, then go for it. But to blame Mandrake because your patchwork > upgrade breaks a beta version of KDE is just dumb. If you're not prepared > for problems, don't run beta software. > Hmmm... add to that Beta software downloaded from a directory named "unsupported" with a README that tells you it is unsupported :-) Also, try sending a note to the packager, he may be willing to help you after he reads the other 200 emails in his inbox. -Chris
Re: [expert] kcontrol STILL doesn't function - DONE/FIXED
On Saturday 03 February 2001 09:57 am, you wrote: > You have reinstalled kde2.1 on a clean install of 7.2? OK, try this: > > Delete your .kderc, do an rm -rf on your $HOME/.kde directory, and then > delete everything in your $HOME/tmp AND as root delete everything in the > system /tmp directory. > > Reboot (actually rebooting may be overkill but be radical). Login. At > this point you get the default kde session. Open kcontrol. It SHOULD be > working now. I hope there is somebody who will try this one for me. I just deleted the temp/kde-alluserswithoutworkingkcontrol/ksycoca files and logged out and in. Kde rebuilt the ksycoca files (probably using kbuildsycoca) and now kcontrol works for all users. I also deleted one user $HOME/.kde directory but I don't think that had anything to do with the fix. I want to test it by crashing kcontrol again but I'm having problems doing that. Maybe it's fixed good this time or maybe it'll crash again. But until then would someone with a broken kcontrol please try deleting the temp/kde-alluserswithoutworkingkcontrol/ksycoca files and log out and in and see if it fixes kcontrol? -- Kelley Terry <[EMAIL PROTECTED]
Re: [expert] kcontrol STILL doesn't function - DONE/FIXED
On Saturday 03 February 2001 03:11 am, 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, Thanks Zeljko for the advice on the file associations tip to fix konqueror to open url links. It works great. I've used menudrake however I've never touched the /configuration/kde directory. I have used the reload user config or reload system config under the file button option at the top often. Strange thing, even though kcontrol is empty again (for the umpteenth time) I still have access to all of it's menu entries through /panel/kmenu button/Configuration/KDE/. -- Kelley Terry <[EMAIL PROTECTED]
Re: [expert] kcontrol STILL doesn't function - DONE/FIXED
You have reinstalled kde2.1 on a clean install of 7.2? OK, try this: Delete your .kderc, do an rm -rf on your $HOME/.kde directory, and then delete everything in your $HOME/tmp AND as root delete everything in the system /tmp directory. Reboot (actually rebooting may be overkill but be radical). Login. At this point you get the default kde session. Open kcontrol. It SHOULD be working now. Go to the file associations menu. Go to html under text. Add konqueror (when you select the add button, just type in "konqueror", do not go down the list and select Konqueror Web Browser). Now select it in the window and move it above Quanta. Select the Embedding tab at the top. On this page the window will have "KHTML" in it. Select "Add" and then go down the list you get and find "Konqueror". Select it. Move it above KHTML. Hit "Apply". Now your html links should work. This worked for me. Now links in kmail actually open up in konqueror as they should and Quanta doesn't open up in its stead. On Friday 02 February 2001 23:30, you wrote: > On Friday 02 February 2001 01:59 pm, you wrote: [...] > > 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 [...] > 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 [...] -- Against stupidity, the gods themselves contend in vain.
Re: [expert] kcontrol STILL doesn't function - DONE/FIXED
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.
Re: [expert] kcontrol STILL doesn't function - DONE/FIXED
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,
Re: [expert] kcontrol STILL doesn't function - DONE/FIXED
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]
Re: [expert] kcontrol STILL doesn't function - DONE/FIXED
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. -- Against stupidity, the gods themselves contend in vain.
Re: [expert] kcontrol STILL doesn't function
On Friday 02 February 2001 08:33, you wrote: > 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. In the 2.1 Beta 2 README the "official" procedure says to install onto a clean 7.2. I'm not a rocket scientist and I have no idea what changes internally from one version of KDE to another. Since I'd already updated from 2.0 to 2.0.1 to 2.1-20001229 to 2.1 Beta...I decided to follow the official procedure and install Beta 2 over a clean 7.2. That's what I did and it works. 2.1 Beta 2 is the most stable KDE I've ever used. Maybe you don't need to do a clean install. Maybe only KDE, CUPS, xinitrc, egcs, ghostscript, arts, jkd, etc. need to be updated. If you know what you're doing, then go for it. But to blame Mandrake because your patchwork upgrade breaks a beta version of KDE is just dumb. If you're not prepared for problems, don't run beta software. M. -- Michael O'Henly TENZO Design
Re: [expert] kcontrol STILL doesn't function
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 /usr/share/applnk directory to /.kde/share and restart kde.
Re: [expert] kcontrol STILL doesn't function
On Friday 02 February 2001 10:27, you wrote: > On Friday 02 February 2001 17:33, you wrote: > > 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... > > No it is not. Just reinstall KDE. > > >and if that is how Mandrake > > is supposed to work, it is going to LOSE people instead of gain them. > > RPM's you downloaded are unsuported by Mandrake. They are NOT official > Mandrake release. Read the readme file on site where you downloaded it. If > you have read it you would never had any problems with Kcontrol > I downloaded them, isstalled them in specefic order and everything works > perfectly. So one would think. I DID read the readme. Nonetheless, my problem exists. I did nothing to my applnks. As a matter of fact, I deleted them along with everything else related to kde in my $HOME directory and re-logged on. Thus, any breakage of applnks is entirely the work of kde, not me. As for being unsupported, yes they are officially unsupported, but they are no different from the "supported" cooker versions EXCEPT that they are compiled with glibc2.1 rather than 2.2. Not an important difference, especially since most other distros with the KDE2.1 available and supported used glibc2.1 too. Glibc2.1 isn't broken so there is no reason distro-X wouldn't support it. It is merely that Mandrake is now using glibc2.2, focused on that entirely, so it isn't going back to deal with pre-glibc2.2 except for security issues. [...] > You know, actually your problem is very simple. You messed up with your > appplication links. Check your applnk directory and see if you removed any > menu group with menudrake. Fix it and your Kcontrol menu entries will > appear again. I would love to do this as it is more elegant that uninstalling, re-downloading, reinstalling. Problem: if an application link is missing, how do I know it is missing? I would have to have a full list of all the applnks that SHOULD be there before I could determine if one is missing. I was wrong, too, by the way. It turns out, at least after running kbuildsycoca, that not even root has a functional kcontrol anymore. -- Against stupidity, the god's themselves contend in vain.
Re: [expert] kcontrol STILL doesn't function
Hi. First off, I will try your variation of not only deleting .kde/ but also tmp/* and see what happens. This is incredibly frustrating. In any case, yes, I have rebooted, restarted X, deleted .kde/, deleted .kderc, and then rebooted and logged in. I have tried it without rebooting and I have also tried just restarting X. In each case, it acts like it is starting kde for the first time when I log in. I have to redo my settings, lookandfeel, etc...but NOT via the Control Center because it doesn't work. Instead, I go directly to the settings directory in the KDE menu under Configuration -> KDE -> . To setup konqueror, I start it and go thru the Settings menu item. I cannot use kcontrol because it is blank. In addition, kcontrol in the KDE menu isn't in the main menu, but is placed in an unnamed folder. If I go to my .kde/ directory, this unnamed folder has the nonsense name of "p^?" . Within this folder is Kcontrol.desktop. Now, this SHOULD be a simple question with a direct answer but no one offers the answer. Kcontrol likely uses some configuration file(s) (beyond kcontrolrc). ONE of these files contains the X-KDE-BaseGroup=settings entry that it needs. What is the name of this file? Where is it supposed to reside? Why doesn't anyone have an answer to this? If I knew where it was/what it's name was, I could do what a NON-newbie would do and simply fix that file. Instead, I am told to do what a newbie would do - uninstall everything and then reinstall. No. I want the simple answer to the simple questions above FIRST. I can try to fix it without wasting time downloading, uninstalling, reinstalling, etc. If it doesn't work, THEN I will go thru the trouble. So, ANYONE? What file does kcontrol look to for X-KDE-BaseGroup=settings? There IS such a file, obviously. If we all knew what it was, then it is likely that many of us with this problem could fix it without pulling a "newbie" and uninstalling, reinstalling, etc. There is a simple problem with a simple correction that likely requires the placement of a misplaced file in the proper place OR it requires a simple edit to some file OR the elimination of a duplicate. Anyone? Surely someone connected to KDE or Mandrake knows where X-KDE-BaseGroup=settings is located. On Friday 02 February 2001 10:58, you wrote: > Kinda, hate to ask this, but have you rebooted??? > I need to find my notes on how I fixed this problem. > I did rm -rf ~/.kde*, and /tmp/*, and I forget what the > last thing was (of course it was the one that worked) > > Brian > > -Original Message- > From: Zeljko Vukman [mailto:[EMAIL PROTECTED]] > Sent: Friday, February 02, 2001 12:28 PM > To: [EMAIL PROTECTED] > Subject: Re: [expert] kcontrol STILL doesn't function > > On Friday 02 February 2001 17:33, you wrote: > > 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... > > No it is not. Just reinstall KDE. > > >and if that is how Mandrake > > is supposed to work, it is going to LOSE people instead of gain them. > > RPM's you downloaded are unsuported by Mandrake. They are NOT official > Mandrake release. Read the readme file on site where you downloaded it. If > you have read it you would never had any problems with Kcontrol > I downloaded them, isstalled them in specefic order and everything works > perfectly. [...] > > You know, actually your problem is very simple. You messed up with your > appplication links. Check your applnk directory and see if you removed any > menu group with menudrake. Fix it and your Kcontrol menu entries will > appear -- Against stupidity, the god's themselves contend in vain.
RE: [expert] kcontrol STILL doesn't function
Kinda, hate to ask this, but have you rebooted??? I need to find my notes on how I fixed this problem. I did rm -rf ~/.kde*, and /tmp/*, and I forget what the last thing was (of course it was the one that worked) Brian -Original Message- From: Zeljko Vukman [mailto:[EMAIL PROTECTED]] Sent: Friday, February 02, 2001 12:28 PM To: [EMAIL PROTECTED] Subject: Re: [expert] kcontrol STILL doesn't function On Friday 02 February 2001 17:33, you wrote: > 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... No it is not. Just reinstall KDE. >and if that is how Mandrake > is supposed to work, it is going to LOSE people instead of gain them. RPM's you downloaded are unsuported by Mandrake. They are NOT official Mandrake release. Read the readme file on site where you downloaded it. If you have read it you would never had any problems with Kcontrol I downloaded them, isstalled them in specefic order and everything works perfectly. >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. Once again, you do not need to totally reinstall your distro. Just KDE. >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. Have you ever heard about 'urpme qt' command? >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? > You know, actually your problem is very simple. You messed up with your appplication links. Check your applnk directory and see if you removed any menu group with menudrake. Fix it and your Kcontrol menu entries will appear again. Best regards,
Re: [expert] kcontrol STILL doesn't function
On Friday 02 February 2001 17:33, you wrote: > 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... No it is not. Just reinstall KDE. >and if that is how Mandrake > is supposed to work, it is going to LOSE people instead of gain them. RPM's you downloaded are unsuported by Mandrake. They are NOT official Mandrake release. Read the readme file on site where you downloaded it. If you have read it you would never had any problems with Kcontrol I downloaded them, isstalled them in specefic order and everything works perfectly. >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. Once again, you do not need to totally reinstall your distro. Just KDE. >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. Have you ever heard about 'urpme qt' command? >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? > You know, actually your problem is very simple. You messed up with your appplication links. Check your applnk directory and see if you removed any menu group with menudrake. Fix it and your Kcontrol menu entries will appear again. Best regards,
Re: [expert] kcontrol STILL doesn't function
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.
Re: [expert] kcontrol STILL doesn't function
Have you considered doing a clean install of 7.2 and then just going straight to the KDE2.1 Beta 2? (That's what I did and I've have almost no problems. It's the most stable KDE2 that I've used yet.) It could be that moving from one update to another is causing the instability. M. On Thursday 01 February 2001 14:58, you wrote: > What switches should be run with kbuildsycoca? I ran kbuildsycoca by > itself but this didn't fix anything. I still have a useless kcontrol. > > 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. > > [...] > > > 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 > > [...] -- Michael O'Henly TENZO Design
Re: [expert] kcontrol STILL doesn't function
What switches should be run with kbuildsycoca? I ran kbuildsycoca by itself but this didn't fix anything. I still have a useless kcontrol. 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. [...] > 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 [...] -- Against stupidity, the god's themselves contend in vain.
RE: [expert] kcontrol STILL doesn't function
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: Kelley Terry [mailto:[EMAIL PROTECTED]] Sent: Monday, January 29, 2001 8:43 PM To: [EMAIL PROTECTED] Subject: Re: [expert] kcontrol STILL doesn't function On Monday 29 January 2001 11:54 am, you wrote: > I just installed the latest KDE2.1 beta for 7.2. All now seems OK (after I > again deleted my .kde/ directory and re-setup everything AGAIN) except > kcontrol. Kcontrol, as with the previous 2.1 iterations, will not work for > user. As superuser, if I start kcontrol from a terminal, it works. As a > user, it produces a useless, empty menu selection field. REPEATED > deletions of .kde and even .kderc followed by re-logins fails to fix it. > It doesn't work. > > How does one get the #&@%!!! kcontrol to work? It also keeps putting > itself into a nameless folder in the kmenu rather than properly sitting > there by itself. > > Anyone? Consider yourself lucky. My kcontrol got messed up when I was doing maintenance as root. Now the kcontrol has an empty menu window for not only root but every user. I've tried moving .kde and then logging in again. It still wouldn't work but at least I could restore the old .kde directory again afterwards. Kelley Terry <[EMAIL PROTECTED]>
RE: [expert] kcontrol STILL doesn't function
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 ;> -- Tom Brinkman[EMAIL PROTECTED]Galveston Bay On Monday 29 January 2001 07:42 pm, Kelley Terry wrote: > On Monday 29 January 2001 11:54 am, you wrote: > > I just installed the latest KDE2.1 beta for 7.2. All now seems OK > > (after I again deleted my .kde/ directory and re-setup everything > > AGAIN) except kcontrol. Kcontrol, as with the previous 2.1 > > iterations, will not work for user. As superuser, if I start > > kcontrol from a terminal, it works. As a user, it produces a > > useless, empty menu selection field. REPEATED deletions of .kde and > > even .kderc followed by re-logins fails to fix it. It doesn't work. > > > > How does one get the #&@%!!! kcontrol to work? It also keeps putting > > itself into a nameless folder in the kmenu rather than properly > > sitting there by itself. > > > > Anyone? > > Consider yourself lucky. My kcontrol got messed up when I was doing > maintenance as root. Now the kcontrol has an empty menu window for not > only root but every user. I've tried moving .kde and then logging in > again. It still wouldn't work but at least I could restore the old > .kde directory again afterwards. > > Kelley Terry <[EMAIL PROTECTED]>
RE: [expert] kcontrol STILL doesn't function
-Original Message- From: Kelley Terry [mailto:[EMAIL PROTECTED]] Sent: Monday, January 29, 2001 8:43 PM To: [EMAIL PROTECTED] Subject: Re: [expert] kcontrol STILL doesn't function On Monday 29 January 2001 11:54 am, you wrote: > I just installed the latest KDE2.1 beta for 7.2. All now seems OK (after I > again deleted my .kde/ directory and re-setup everything AGAIN) except > kcontrol. Kcontrol, as with the previous 2.1 iterations, will not work for > user. As superuser, if I start kcontrol from a terminal, it works. As a > user, it produces a useless, empty menu selection field. REPEATED > deletions of .kde and even .kderc followed by re-logins fails to fix it. > It doesn't work. > > How does one get the #&@%!!! kcontrol to work? It also keeps putting > itself into a nameless folder in the kmenu rather than properly sitting > there by itself. > > Anyone? Consider yourself lucky. My kcontrol got messed up when I was doing maintenance as root. Now the kcontrol has an empty menu window for not only root but every user. I've tried moving .kde and then logging in again. It still wouldn't work but at least I could restore the old .kde directory again afterwards. Kelley Terry <[EMAIL PROTECTED]>
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 ;> -- Tom Brinkman[EMAIL PROTECTED]Galveston Bay On Monday 29 January 2001 07:42 pm, Kelley Terry wrote: > On Monday 29 January 2001 11:54 am, you wrote: > > I just installed the latest KDE2.1 beta for 7.2. All now seems OK > > (after I again deleted my .kde/ directory and re-setup everything > > AGAIN) except kcontrol. Kcontrol, as with the previous 2.1 > > iterations, will not work for user. As superuser, if I start > > kcontrol from a terminal, it works. As a user, it produces a > > useless, empty menu selection field. REPEATED deletions of .kde and > > even .kderc followed by re-logins fails to fix it. It doesn't work. > > > > How does one get the #&@%!!! kcontrol to work? It also keeps putting > > itself into a nameless folder in the kmenu rather than properly > > sitting there by itself. > > > > Anyone? > > Consider yourself lucky. My kcontrol got messed up when I was doing > maintenance as root. Now the kcontrol has an empty menu window for not > only root but every user. I've tried moving .kde and then logging in > again. It still wouldn't work but at least I could restore the old > .kde directory again afterwards. > > Kelley Terry <[EMAIL PROTECTED]>
Re: [expert] kcontrol STILL doesn't function
On Monday 29 January 2001 11:54 am, you wrote: > I just installed the latest KDE2.1 beta for 7.2. All now seems OK (after I > again deleted my .kde/ directory and re-setup everything AGAIN) except > kcontrol. Kcontrol, as with the previous 2.1 iterations, will not work for > user. As superuser, if I start kcontrol from a terminal, it works. As a > user, it produces a useless, empty menu selection field. REPEATED > deletions of .kde and even .kderc followed by re-logins fails to fix it. > It doesn't work. > > How does one get the #&@%!!! kcontrol to work? It also keeps putting > itself into a nameless folder in the kmenu rather than properly sitting > there by itself. > > Anyone? Consider yourself lucky. My kcontrol got messed up when I was doing maintenance as root. Now the kcontrol has an empty menu window for not only root but every user. I've tried moving .kde and then logging in again. It still wouldn't work but at least I could restore the old .kde directory again afterwards. Kelley Terry <[EMAIL PROTECTED]>
