Clean install of the Kmenu?

[Wallex]

When I try to open the K menu editor... lately it becomes more and more likely to fail, today it didn't work until the fifteenth or so try. So, I ran it from the konsole to see what was the problem, and lookie here....
kmenuedit
QDir::readDirEntries: Cannot read the directory: /home/wallex/.kde/share/applnk/ .kmenuedit_clipboard
QDir::readDirEntries: Cannot read the directory: /home/wallex/.kde/share/applnk/ .kmenuedit_clipboard
kdecore (KLibLoader): WARNING: library=/usr/lib/libsocks.so: file=/usr/lib/libsocks.so: /usr/lib/libsocks.so: cannot open shared object file: No such file or directory
kdecore (KLibLoader): WARNING: library=/usr/lib/libsocks5.so: file=/usr/lib/libsocks5.so: /usr/lib/libsocks5.so: cannot open shared object file: No such file or directory
kdecore (KLibLoader): WARNING: library=/usr/lib/libsocks5_sh.so: file=/usr/lib/libsocks5_sh.so: /usr/lib/libsocks5_sh.so: cannot open shared object file: No such file or directory
kdecore (KLibLoader): WARNING: library=/usr/local/lib/libsocks.so: file=/usr/local/lib/libsocks.so: /usr/local/lib/libsocks.so: cannot open shared object file: No such file or directory
kdecore (KLibLoader): WARNING: library=/usr/local/lib/libsocks5.so: file=/usr/local/lib/libsocks5.so: /usr/local/lib/libsocks5.so: cannot open shared object file: No such file or directory
kdecore (KLibLoader): WARNING: library=/usr/local/lib/libsocks5_sh.so: file=/usr/local/lib/libsocks5_sh.so: /usr/local/lib/libsocks5_sh.so: cannot open shared object file: No such file or directory
kdecore (KLibLoader): WARNING: library=/usr/local/socks5/lib/libsocks.so: file=/usr/local/socks5/lib/libsocks.so: /usr/local/socks5/lib/libsocks.so: cannot open shared object file: No such file or directory
kdecore (KLibLoader): WARNING: library=/usr/local/socks5/lib/libsocks5.so: file=/usr/local/socks5/lib/libsocks5.so: /usr/local/socks5/lib/libsocks5.so: cannot open shared object file: No such file or directory
kdecore (KLibLoader): WARNING: library=/usr/local/socks5/lib/libsocks5_sh.so: file=/usr/local/socks5/lib/libsocks5_sh.so: /usr/local/socks5/lib/libsocks5_sh.so: cannot open shared object file: No such file or directory
kdecore (KLibLoader): WARNING: library=/opt/socks5/lib/libsocks.so: file=/opt/socks5/lib/libsocks.so: /opt/socks5/lib/libsocks.so: cannot open shared object file: No such file or directory
kdecore (KLibLoader): WARNING: library=/opt/socks5/lib/libsocks5.so: file=/opt/socks5/lib/libsocks5.so: /opt/socks5/lib/libsocks5.so: cannot open shared object file: No such file or directory
kdecore (KLibLoader): WARNING: library=/opt/socks5/lib/libsocks5_sh.so: file=/opt/socks5/lib/libsocks5_sh.so: /opt/socks5/lib/libsocks5_sh.so: cannot open shared object file: No such file or directory
ryel@Ryel:~> kmenuedit: WARNING: KLocale: trying to look up "" in catalogue. Fix the program

After seeing all that, I was amazed the program still works. Obviously.. I have to Fix the program somehow, I was thinking about doing a clean install and repopulating the Kmenu myself, but is this even possible? Or anyone knows of any other way to go around and fix this?

[JohnT]

What distro are you running?
Which KDE ver?

[Wallex]

Well, the splash screen says it's KDE 3.0, despite the fact that when I do rpm -q qt I get: qt-2.3.2-138 (and I thought KDE3.0 would most absolutely NEED Qt 3 as well). As for the Distro... well, read the sig. Hmm... I'll go check red-carpet to see if there are any updates for my distro, maybe one of those could help.

[mdwatts]

Try

rpm -q qt3
or
rpm -qa | grep qt

[Wallex]

Lookie here...
qt3-3.0.3-15
qt3-non-mt-3.0.3-14
yast2-ui-qt-2.5.17-4
qt-2.3.2-138
So I have all these... weird. Anyway... noone has quite told me if I could just uninstall and reinstall that K bar (or some other way to fix that huge load of problems it has), or should I just disregard it? Not all problems have to be fixed afterall...

[mdwatts]

Have you done any searches for those error messages?

Looked to see if those libraries exist?

Found out what package(s) contain those libraries and checked to see if they are installed?

[Wallex]

Uh.... no? I feel dumb now. I'll go read the manual for kmenuedit and then do a search for those socks5 libs or whatever package contains it.. altough I doubt I really need them, so instead I'll go look for what is causing this problem. Again... I get scared too easily by 'hundred lines error messages'.

[JohnT]

socks5lib, IMO shouldn't be associated with the menu configs in any respect. Unless it's a call to an app you've removed or moved. If you've done so, remove or move the app in your menu line-up.

[Wallex]

Soooo right. Maybe it has to do with one of the icons of the programs I added? I think I'll clean that menu and try to start again from zero... altough most of the folders there are not 'deleteable', really strange... well, I must go deal with other things now, so I'll play with that menu later.
EDIT: Weird... I can't delete any of the entries in the kmenu! I think I don't have access to whatever is the file I should be modifying when using this... gee, I wished there was a man page for the kmenu, but there seems to be none... I wonder how I'll get this fixed now...

[JohnT]

Originally posted by Wallex
Soooo right. Maybe it has to do with one of the icons of the programs I added? I think I'll clean that menu and try to start again from zero... altough most of the folders there are not 'deleteable', really strange... well, I must go deal with other things now, so I'll play with that menu later.
EDIT: Weird... I can't delete any of the entries in the kmenu! I think I don't have access to whatever is the file I should be modifying when using this... gee, I wished there was a man page for the kmenu, but there seems to be none... I wonder how I'll get this fixed now...

Don't you have some type of menu editor in Suse?
There are system menu items and root menu items is why some are not deletable from one.

[mdwatts]

I don't know if this is the cause to those errors, but do you have SOCKS enabled in the KDE Control Center under Network/SOCKS?

[Wallex]

Weirdness...
I went to the KDE control, and the Socks is on, but when I try to test it, no Socks could be detected. So... for some reason the socks does not starts. That is a problem.. or is not, since I don't think I really need socks anyway. As for the menu Editor... that K menu editor is plain WEIRD.
When I modify it, it does NOT modifies the standard K menu you normally see, that K menu seems impossible to customize (maybe it's autoconfigured according to what is installed through Yast)
What I DO configure, are the menu entries that will appear if I 'add' a menu (I basically 'copied' the whole K menu and added it as a different button, and removed the standard K button). And when I said I couldn't remove the entries, I meant the very entries that I added in the past, this is most likely because the K menu uses a config file 'somewhere' out of my home's dir. When it starts it complains that I don't have a ~/.kde/share/applnk/.kmenuedit_clipboard directory. I guess that's the 'personal' menu, what I do is create that dir, and guess what happens? Kmenuedits deletes that directory! Why it wants that dir if it's going to delete it when I create it? Oh well... I think I'll just run it from root, and delete everything, then start again from zero. if I ever need a program that's not there... well, I always have alt+f1 to access the original K menu.
EDIT: Ah the power of a newbie... I couldn't delete any of the components, but nothing stopped me from cutting them without pasting. So.. the menu is now back to normal, but those error messages still appear. I wonder.... think those problems where there ALL the time? Afterall, it wasn't until recently that I started running kmenuedit from the command line (and that was because it wouldn't start up) that I noticed all those 'problems'.

[JohnT]

Is it deleting the directory or just hiding it? Turn on the view in the drop-down menu.

[Wallex]

It really is deleting it... it's the 'cut' command afterall. Don't worry, it didn't allow me to delete the original menu items. That K menu is pretty new now, I am filling it up from zero. I am sort of ignoring that socks5 problem now... afterall, it does works, and if it ain't broken, don't fix it.

[mdwatts]

Disable SOCK in the KDE Control Center as you shouldn't need it.

[Wallex]

Hey that was a good idea!
I am not sure what is that 'socks' support thing for, the only socks use that I know is for running applications over a proxy, altough most programs already come with that included... unless it's meant for other computers on my LAN to access the internet through my pc using proxy? I guess that's probably it. But since I am using a gateway, no need for that. Now the Kmenuedit only gives me the error:QDir::readDirEntries: Cannot read the directory: /home/wallex/.kde/share/applnk/.kmenuedit_clipboard
Which is funny because each time I create that dir, the program deletes it. Well, from 30 or so errors down to one, that's a big improvement. Altough that 'error' doesn't stops me from using the application, so it really doesn't matters. Thanks.