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
