Re: [Cooker] How to get rid of "KDEInit could not launch 'kfmclient'" message?
On Mon 24 Mar 2003 06:56, Pixel posted as excerpted below: > Duncan <[EMAIL PROTECTED]> writes: > > .. I was pretty disgusted with DiskDrake as well, after I'd put a bunch > > of comments in detialing the various mount options, ran DiskDrake, and > > not only had it delete or mix up the comments and order, but actually > > uncomment a bunch of stuff, so that when I rebooted, I had a bunch of > > root mount points like /this /option /is /pretty /useful, etc! > > please send the non-screwed fstab That was an entiremajor Mdk release ago now (8.1). I'm hoping something like that isn't still around, altho like I said I haven't tried it lately. I'd send it now, certainly, as that was one of the reasons I got on the list, but back then I was new enough to Linux for all I knew that was expected behavior, and the GUI tool was ONLY for those not willing to venture into /etc with nothing more than a text editor and a file browser. I'll try it again, tho, and post if a similar problem still exists.. Thx. -- Duncan "They that can give up essential liberty to obtain a little temporary safety, deserve neither liberty nor safety." -- Benjamin Franklin
Re: [Cooker] How to get rid of "KDEInit could not launch 'kfmclient'" message?
On Wed 19 Mar 2003 17:05, Charles Shirley posted as excerpted below: > While a bugfix is made, there is a way to manually correct this bug. You > have to copy the files kfmclient.desktop, kfmclient_dir.desktop, > kfmclient_html.desktop and kfmclient_war.desktop from > /usr/share/applnk/System/ to your ~/.kde/share/applnk-mdk/ directory. This > will fix the annoying dialog pop-up. That might explain why I don't have the problem here. Since I'm the only one on my box, and I didn't like the various menu versions differing between root and my various user alter-egos, I deleted all the user ones, and reset them as symlinks to the main /usr/share system menus. Of course, that means I can't change the menu around except by executing a kdesu menudrake, but that's fine by me, as at least I maintain consistency between my various logins, that way. .. I remember what I terrible time I had when I started. I spent a lot of time reorganizing the menus as I wanted them, using the .desktop KMenu file system menu idea, which seemed natural, since that's what MSWormOS uses as well, and I was used to doing it there. .. Then I updated, and MY MENUS WERE ALL SCREWED UP AGAIN. I WAS **NOT** HAPPY!! I'd spent hours tweaking it just the way I wanted, only to have all my work erased. Eventually, I figured out that I had to use MenuDrake to get it to stick, and then I was OK, but it took me several trial and error retries before I figured that out. .. The other thing that nabbed me was the unexpected fact that file types were linked in with the menu entries. When I moved around the menu entries, KDE couldn't find the applications, which I thought was really strange, as from MSWormOS I was used to being able to do what I wanted with the menu UI, without having to worry about file type associations at all. I had been rather a power user on MSWormOS. Needless to say, I was rather incredibly frustrated with Mdk/KDE/Linux, until I figured out a bit more about it. I still don't know where it stores EVERYTHING, but I can modify most stuff now w/o messing things up, and know how to go about finding the raw text files to change if I decide I need to. .. I was pretty disgusted with DiskDrake as well, after I'd put a bunch of comments in detialing the various mount options, ran DiskDrake, and not only had it delete or mix up the comments and order, but actually uncomment a bunch of stuff, so that when I rebooted, I had a bunch of root mount points like /this /option /is /pretty /useful, etc! Fortunately, by then I knew enough about the system to recognize pretty quickly what had happened, and go "unscrew" my fstab file. I don't know if that was fixed or not, because now, when I run DiskDrake, I do all the partition setup and formatting, etc, but do NOT let it write to fstab. As well, any highly modified files like that and my XF86Config (as I have two vid cards running three monitors, and Xinerama), I keep several copies of, in case something munches on them for breakfast, or something, like DiskDrake did to my fstab file that time. Actually, that's one reason why I'm on this list, now. I want to be able to report and get feedback on such things, as well as getting them fixed b4 they move from Cooker to general distribution. -- Duncan "They that can give up essential liberty to obtain a little temporary safety, deserve neither liberty nor safety." -- Benjamin Franklin
Re: [Cooker] How to get rid of "KDEInit could not launch 'kfmclient'" message?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I know this won't be that much help, since I can't remember exactly what I did...but I was having this same problem, and finally found that there was, (i think) a mimeinfo error... like it was trying to open it with the default of konqueror -caption %1 (I can't remember exactly) instead of kfmclient openProfile filemanagement I think I did the simple thing of right clicking on a folder and choosing open with 'kfmclient openProfile filemanagement' and checking the "remember application association for this type of file" box... Also...although, and this may have been because I've updated since then the current thing is 'kfmclient openURL %u inode/directory' which is in the /usr/share/applnk/System/kfmclient_dir.desktop file You can check what your system is set to by going into the Configure File Associations section of the Konqueror settings... Go to inode then choose directory, and see whats there... I've got Konqueror as above, and an entry for Cervisia... On Thursday 20 March 2003 12:44 am, James Sparenberg wrote: > On Wed, 2003-03-19 at 14:24, Clive Dove wrote: > > I am still seeing this message whenever I open a desktop folder. > > > > Is there any way to get rid of it? > > > > Before anyone asks, I did update the packages today. > > Had something like this happen to me before. What was recommended to me > and I might add worked, was to update my locate db then do > > locate rpmnew > > then go through my box and mv the xxx.rpmnew files to the correct name > (bearing in mind changes I made to the original) Could solve your > problem could not. > > James -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+eVqNJPZHtex3jVcRAoT3AJ48uoHNmPzrO3Zg4zLfyY82Q0kDwACgtwb9 q1y/hg0yOjffjDmiyDJk1C8= =rHhj -END PGP SIGNATURE-
Re: [Cooker] How to get rid of "KDEInit could not launch 'kfmclient'" message?
On Wednesday 19 March 2003 19:05, Charles Shirley wrote: > On Wednesday 19 March 2003 17:24, Clive Dove wrote: > >I am still seeing this message whenever I open a desktop folder. > > > >Is there any way to get rid of it? > > > >Before anyone asks, I did update the packages today. > > Hi Clive, > There is a workaround posted in the bugzilla entry > [Bug 1471]. It solved the problem for me. The bug is very > long, so below I have included the snippet with the work- > around: > > --- Additional Comments From [EMAIL PROTECTED] > 2003-02-23 20:24 --- While a bugfix is made, there is a way to > manually correct this bug. You have to copy the files > kfmclient.desktop, kfmclient_dir.desktop, kfmclient_html.desktop and > kfmclient_war.desktop from /usr/share/applnk/System/ to your > ~/.kde/share/applnk-mdk/ directory. This will fix the annoying dialog > pop-up. > > I hope this can help those for whom the problem persists. > My guess is that it occurs on systematically upgraded > systems, but not on clean installs. (I have not done a > complete install in over one year...) > > --Chuck I have gotten rid of the error message using the thread in Bugzilla bug 1471. Thank you for calling it to my attention. It appears that this bug has acquired multiple Bugzilla numbers and I had not read 1471.
Re: [Cooker] How to get rid of "KDEInit could not launch 'kfmclient'"message?
On Wednesday 19 March 2003 17:24, Clive Dove wrote: >I am still seeing this message whenever I open a desktop folder. > >Is there any way to get rid of it? > >Before anyone asks, I did update the packages today. Hi Clive, There is a workaround posted in the bugzilla entry [Bug 1471]. It solved the problem for me. The bug is very long, so below I have included the snippet with the work- around: --- Additional Comments From [EMAIL PROTECTED] 2003-02-23 20:24 --- While a bugfix is made, there is a way to manually correct this bug. You have to copy the files kfmclient.desktop, kfmclient_dir.desktop, kfmclient_html.desktop and kfmclient_war.desktop from /usr/share/applnk/System/ to your ~/.kde/share/applnk-mdk/ directory. This will fix the annoying dialog pop-up. I hope this can help those for whom the problem persists. My guess is that it occurs on systematically upgraded systems, but not on clean installs. (I have not done a complete install in over one year...) --Chuck -- +-% He's a real UNIX Man $-+-+ \ Sitting in his UNIX LAN \ Charles A. Shirley \ \ Making all his UNIX plans \ cashirley (at) comcast (dot) net \ +--# For nobody @--+-+
