On 3/15/07, Tom Spear speeddymon@gmail.com wrote:
On 3/15/07, Lei Zhang thestig@google.com wrote:
It looks like the icon bug has already been reported: http://bugs.winehq.org/show_bug.cgi?id=7084
On my machine, wine puts WinRar.desktop in ~/.local/shared/applications/wine/Programs/WinRar, which then appears in my KDE menu. Are you saying the .desktop files went into ~/.wine/drive_c/Program Files/WinRar instead?
Yes, except that my Drive C is mapped to /mnt/d but that shouldnt make any difference. Note that this happens with the 2.6.20.2 kernel from kernel.org, which the 2.6 kernel is now required in order to run wine on Slackware 11..
Now that I think about it, I cant get wine to run on the Slack 11 2.4 kernel because of missing kernel support for something, so I had to get the 2.6 kernel from kernel.org..
When I originally installed this box, the current 2.6 was 2.6.20.1 and wine installed WinRAR to the menu and the desktop properly. Then I broke my install and had to to a clean reinstall of Slack, and so when I went back to kernel.org, the kernel was 2.6.20.2, so I downloaded it and compiled and installed.. After that I installed wine, and the menu shortcuts were put in the wrong folder. Perhaps I either missed a config option in the kernel that is affecting this, or something that was changed in 2.6 actually breaks wine's menu creation?
Like I said, the wine version didn't change between the reinstalls because I can't use git....
-- Thanks
Tom
Check out this new 3D Instant Messenger called IMVU. It's the best I have seen yet!
http://imvu.com/catalog/web_invitation.php?userId=1547373&from=power-ema...
I did some more checking into this just now. I'm not sure why or how, but when I installed Worms 2, it installed the menu entries properly. So I uninstalled WinRAR and reinstalled it. This time it created a menu entry for WinRAR under the wine folder in the menu, but it isnt a subfolder, like it should be and the other icons that should be in the menu aren't there. It appears that the winrar installer may be doing something that other installers dont do....
Anyone know of any debug messages I should run to try to narrow down the problem?