[SOLVED] WINE and Slackware64. Programs Only Run in a Terminal.
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,095
Rep:
WINE and Slackware64. Programs Only Run in a Terminal.
Once again, I would like to say a word of Thanks to Mr. Volkerding, Alien BOB, and the entire Slackware team for a job very well done on Slackware64.
Alien BOB's work on Slackware64, his "True Multilib"* files, and his latest creation, a 64 bit package of WINE, is truly outstanding and way beyond "the call of duty."
*You should copyright that Alien BOB and/or make it a registered trademark.
I did a search of the last month's posts and didn't see anything about this problem (in the Slackware forum).
After installing Slackware64 and the "True Multilib" files, I installed the same version of WINE that worked so well with Slackware 12.2. Unfortunately, I found that while a windows application would run if it was fired it up from the prompt in a terminal (Konsole), it would not work, using the same command, as an item from the menu.
Thinking perhaps a new version was in order I looked around and found Alien BOB's recent 64 bit package of WINE. BTW, it runs better than any previous
version of WINE I've used. Thanks, again. However, the above outlined problem remains.
Anyone know a fix?
Many Thanks.
Last edited by cwizardone; 09-19-2009 at 04:30 PM.
Reason: Typo.
I thought I could run my Wine-installed programs from their installed menus in Slackware64, but now I am not so sure.. I'll have to wait until I can boot into 64bit to test that (I only have one 64bit computer and that is compiling VLC in 32bit now.)
I have quicken starting from the menu here, however the menu item is one I created not one added by wine. I can start from menu, panel, command line or clicking on an icon. This works in both KDE and XFCE on Slackware64-13.0 (multi-lib) with a stock kernel and wine-1.1.24-x86_64-1_SBo.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,095
Original Poster
Rep:
Quote:
Originally Posted by samac
I have quicken starting from the menu here, however the menu item is one I created not one added by wine. I can start from menu, panel, command line or clicking on an icon. This works in both KDE and XFCE on Slackware64-13.0 (multi-lib) with a stock kernel and wine-1.1.24-x86_64-1_SBo.
samac
What are you doing differently with your commands?
If I enter this command at the prompt in a console,
wine /home/nai/.wine/drive_c/ahdw/ahd3.exe
the program will run. However, if I put that same command in a command line box using the KDE Menu Editor, the program won't run.
I've been trying different options, but no success as of the moment.
BTW, the above command line worked perfectly with WINE in Slackware 12.2.
Thanks.
It is there, I checked, and the permissions are correct, i.e., they are set for my user name and the group, "users."
Just for chuckles I deleted the /drive_c/ahdw directory and re-installed the program from scratch via WINE. Didn't change a thing, still the same problem.
So, I then copied the ahdw directory to my home directory and ran,
wine /home/hai/ahdw/ahd3.exe
in a konsole and it did work. However, it still won't work if ran from a menu entry using the KDE Menu Editor.
It is probably something simple, but none of the tweaks I've tried so far have worked. I've been running this same old windows program, "The American Heritage Talking Dictionary" for years under wine and have always been able to make it work, i.e., until now, for whatever reasons.
I've never been able to get the audio to work, but I'm happy just to have the dictionary and thesaurus at my fingertips.
Anymore suggestions on how to make this work from the menu would be greatly appreciated.
Many Thanks.
Last edited by cwizardone; 09-22-2009 at 11:15 AM.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,095
Original Poster
Rep:
Quote:
Originally Posted by samac
A couple of thoughts which probably have already been done. Is this a newly compiled wine or one that you had lying about? Have you tried wincfg?
samac
Yep. Tried both, old and new, but the result is the same.
Curious. I have 64 bit current with multilib and just installed alien's wine package. It worked for me with double quotes for the path (although i used the notepad.exe)
This might be super obvious, but did you try giving the full path to wine in the menu command?
1) Please post the menu command you're using.
2) In the menu editor advanced tab, select run in terminal. Hopefully you'll get some output if things aren't working OK.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.