Hi Abrecoarc,

Yup, wine won't shop up in your SliTaz menu even if correctly installed. This issue only concerns version 2.0, I've got the same problem.

Well, nope, it is not really a problem, because everything works fine.

Type "winecfg" at command-line prompt to fire up the wine configuration GUI.
Get your prompt in a MS Windows application root directory and type "wine [name of executable.exe]" to fire up the application itself (or to launch a MS Windows software installation, of course).

Hope that helps, regards,

-- Babaorum

Thanks alot for that. but when i type winecfg it gives below error.

tux@slitaz:~$ winecfg
-sh: winecfg: Permission denied
---------------------------------------------------------------
and when i login as root. then also same.

root@slitaz:/home/tux$ winecfg
sh: winecfg: Permission denied
---------------------------------------------------------------

One more thing when i boot slitaz from usb it gave me this error window at desktop.
http://picasaweb.google.com/lh/photo/enGbYTjbGQ7au7c6yY85gw?feat=directlink

is this happening because of this window ?
do i have to install fresh slitaz?
---------------------------------------------------------------

I never had wine denied or a theme error. I would uninstall and reinstall wine (maybe --force at command line after updating system through the package manager).

hmmm I had this error, I remember now. Unluckily, I cannot remember what I've done to leave it behind (I don't have it anymore now).

Yup, you should try to:

1) check user permissions of $HOME/.wine user prefs directory (that you should own as a user and could read+write

2) uninstall then reinstall wine

3) check if an update is necessary

As a remark, I have 1.0.1 version of Wine.

-- Babaorum

:( i got this now.
--------------------------------------------
tux@slitaz:~$ $HOME/.wine
-sh: /home/tux/.wine: not found
--------------------------------------------
have i typed something wrong? :( then how to -check user permissions of $HOME/.wine user prefs directory-

reply me my Angle friend. Sorry if i m making it too busy as i m not a programmer. But i am trying to fix it.

can you just type the command exactly what your saying.

Right-click on an exe to open it with wine.

http://www.winehq.org/

Set your file manager to view hidden files and right click on ~/.wine to view permissions.

You can test by installing another slitaz elsewhere or using the live cd (boot live cd, use package manager to recharge list and update system, install wine on live cd's ram session). If wine works on the other slitaz, you want want to save personal files and reinstall slitaz.

I never used stable but slitaz cooking often breaks after a while or breaks apps for a while and sometimes the apps get better later but I often reinstall the os.

Maybe we should not start yet to confuse Abrecoarc between stable and cooking Slicel, as he claims himself not to be so experimented in Linux as a programmer. But it will be our second option, indeed.

(I'm neither a programmer nor a Linux guru myself)

We will still try to follow the main idea the further way possible.

One thing first: $HOME/.wine is the path to a directory, not to an executable. Typing it at command-line prompt won't success because the shell will wait a command, more exactly an internal command or an executable third party command (a file).
When it replies that it does not find $HOME/.wine, there are two explanations, both "normal":

a ) it speaks truth ! $HOME/.wine viewed as a command was not found

b) maybe you do not have any ".wine" directory in your $HOME directory, which is the normal case until you did run (successfully) wine for the first time

So when I ask you to check for this *directory* user permissions, you typed only the argument, but not the command itself, that is:
ls -ld $HOME/.wine

If it replies that this directory what not found, then we have our answer: it does not exist, it is not necessary then to check permissions of something not existing, right ?

You still have other choices to do before maybe trying Slicel proposition:

2) check if an update is necessary (using TazPkg package manager, I presume that you know how to launch and use it: "recharge lists", then "upgrade").

You can also make the same thing at command-line:

su
(type your root password, that should be "root")
tazpkg recharge && tazpkg upgrade
exit

3) uninstall then reinstall wine (also using TazPkg)

-- Babaorum

Hi abrecoarc,
about you're second problem (gtk+ icon theme), you can :

* Select Tango icons set (the default) in lxappearance (menu->system->prf->appearance or type lxappearance in the terminal)

* If it doesn't solve you're problem, you can reinstall the package with (in root):
tazpkg get-install slitaz-tango-icon --forced
And re-try to select Tango in lxappearance.

the command worked and it gave me this
--------------------------------------------------
tux@slitaz:~$ ls -ld $HOME/.wine
drwxr-xr-x 4 tux tux 4096 Jan 21 21:18 /home/tux/.wine/
--------------------------------------------------

-what the above says about permission?

-when i track the link ´/home/tux/.wine/´ and right click the folder, it gave this
http://picasaweb.google.co.in/lh/photo/cvTbqFY49Z9oO4yjWjBpLg?feat=directlink

that means i have permission. but still when i run ´tux@slitaz:~$ winecfg´
----------------------------------------------
tux@slitaz:~$ winecfg
-sh: winecfg: Permission denied
----------------------------------------------

any hope friends ?
(just to crack a joke) just to make my self happy in these time. I just feel like you give me your slitaz pendrive in which wine is working and i give my which is not. But we both are too far. I m from India,Bombay.
waiting for reply.

Hi abrecoarc,
why run winecfg not as root? Winecfg is likely not in home.

are you there online.

this is the result now when i did as a root.
----------------------------
root@slitaz:/home/tux# winecfg
sh: winecfg: Permission denied
----------------------------
it is same

winecfg should run as normal user because it modify files wich are in /home/tux/.wine

Permissions: It's a directory. The owner has read, write & execution permissions; those in the same group only have read and execute permissions, as do others.

Can you give the result of :
cd /usr/bin
ls -ld wine*

ux@slitaz:~$ cd /usr/bin
tux@slitaz:/usr/bin$
-------------------------------------
tux@slitaz:/usr/bin$ ls -ld wine*
-rwxr-xr-x 1 root root 5172 Apr 16 2009 wine
-rwxr-xr-x 1 root root 18396 Apr 16 2009 wine-kthread
-rwxr-xr-x 1 root root 10920 Apr 16 2009 wine-preloader
-rwxr-xr-x 1 root root 7048 Apr 16 2009 wine-pthread
-rw-r--r-- 14 root root 1582 Mar 12 2009 wineboot
-rw-r--r-- 14 root root 1582 Mar 12 2009 winebrowser
-rwxr-xr-x 1 root root 84028 Apr 16 2009 winebuild
-rw-r--r-- 14 root root 1582 Mar 12 2009 winecfg
-rw-r--r-- 14 root root 1582 Mar 12 2009 wineconsole
lrwxrwxrwx 1 root root 7 Jan 21 23:14 winecpp -> winegcc
-rw-r--r-- 14 root root 1582 Mar 12 2009 winedbg
-rwxr-xr-x 1 root root 125048 Apr 16 2009 winedump
-rw-r--r-- 14 root root 1582 Mar 12 2009 winefile
lrwxrwxrwx 1 root root 7 Jan 21 23:14 wineg++ -> winegcc
-rwxr-xr-x 1 root root 21564 Apr 16 2009 winegcc
-rwxr-xr-x 1 root root 58998 Mar 12 2009 winemaker
-rw-r--r-- 14 root root 1582 Mar 12 2009 winemine
-rw-r--r-- 14 root root 1582 Mar 12 2009 winepath
-rwxr-xr-x 1 root root 3383 Mar 12 2009 wineprefixcreate
-rwxr-xr-x 1 root root 298304 Apr 16 2009 wineserver
-rwxr-xr-x 1 root root 5506 Mar 12 2009 wineshelllink
tux@slitaz:/usr/bin$
--------------------------------------

Ok this is a strange problem... some executables have no permission to execute...
You can solve this with this command, as root :
--------------------------------------
cd /usr/bin
chmod a+x wineboot winebrowser winecfg wineconsole winedbg
winefile winemine winepath
--------------------------------------
Then everything should works correctly

you guys are awesome awesome awesome. You too my angle friend babaorum.

thx
i would like to show you my screenshot.
http://picasaweb.google.co.in/lh/photo/dU5X9D0GciQLZxr0O3ZyFw?feat=directlink

Happy to see it solved. This was indeed a user permission problem.

Just to let you know it:
the user permissions are litterally a string divided in four substrings. Each "slot" for a letter is dedicated to a particular permission, as showed in the following template:

[directory=d|link=l|regular file=-][read=r|nothing=-][write=w|nothing=-][execute=x|nothing=-][read=r|nothing=-][write=w|nothing=-][execute=x|nothing=-][read=r|nothing=-][write=w|nothing=-][execute=x|nothing=-]

- green: owner user permissions (read/write/execute)
- blue: users of same group as owner user permissions (read/write/execute)
- purple: all other user permissions (read/write/execute)

Now you can now what this means and why it did not work:

This file is owned by user but its usage is to be invoked as a non-root user.
It is:

- NOT executable even for its owner (root)
- NOT executable for same group as root (group: root)
- NOT executable for anyone else (and then not executable for YOU)