Photoshop CS6 won't open through q4wine-cli, /usr/bin/wine works

[JKAbrams]

This does not work:

me@mypc / $ q4wine-cli  -p "photoshopcs6" -i "Photoshop CS6"
[ii] loaded: "q4wine_en_us" 
Done
me@mypc / $ [ii] loaded: "q4wine_en_us" 
"--prefix" 
"--nice" 
"--program-bin" 
"--wrkdir" 
Exec string:
env  WINEPREFIX='/home/wine/photoshop'  WINESERVER='/usr/lib/i386-linux-gnu/wine'  WINELOADER='/usr/bin/wine32'  WINEDLLPATH='/usr/lib/i386-linux-gnu/wine/'  WINEARCH='win32'  WINEDEBUG='-all'  /bin/sh -c "cd '/home/wine/photoshop/drive_c/Program Files/Adobe/Adobe Photoshop CS6/' &&   '/usr/bin/wine32'   'Photoshop.exe'  2>&1 "
Exit code:
13568
App STDOUT and STDERR output:

But this works:

me@mypc / $ WINEPREFIX='/home/wine/photoshop' wine /home/wine/photoshop/drive_c/Program\ Files/Adobe/Adobe\ Photoshop\ CS6/Photoshop.exe

And this works:

me@mypc / $ WINEPREFIX='/home/wine/photoshop' WINESERVER='/usr/lib/i386-linux-gnu/wine' WINELOADER='/usr/bin/wine32' WINEDLLPATH='/usr/lib/i386-linux-gnu/wine/'  WINEARCH='win32'  WINEDEBUG='-all' wine /home/wine/photoshop/drive_c/Program\ Files/Adobe/Adobe\ Photoshop\ CS6/Photoshop.exe

However things gets interesting when running with /usr/bin/wine32

me@mypc / $ WINEPREFIX='/home/wine/photoshop' WINESERVER='/usr/lib/i386-linux-gnu/wine' WINELOADER='/usr/bin/wine32' WINEDLLPATH='/usr/lib/i386-linux-gnu/wine/'  WINEARCH='win32'  WINEDEBUG='-all' /usr/bin/wine32 /home/wine/photoshop/drive_c/Program\ Files/Adobe/Adobe\ Photoshop\ CS6/Photoshop.exe 2>&1
wine client error:0: version mismatch 449/431.
Your wine binary was not upgraded correctly,
or you have an older one somewhere in your PATH.
Or maybe the wrong wineserver is still running?

What then is the difference between /usr/bin/wine32 and /usr/bin/wine?

me@mypc / $ ls -l /usr/bin/wine /usr/bin/wine32
lrwxrwxrwx 1 root root   22 Sep  2 18:04 /usr/bin/wine -> /etc/alternatives/wine
-rwxr-xr-x 1 root root 1039 Oct  3  2012 /usr/bin/wine32
me@mypc / $ ls -l /etc/alternatives/wine
lrwxrwxrwx 1 root root 15 Sep  2 18:04 /etc/alternatives/wine -> /usr/bin/wine32

wine is just symlinked back to wine32: /usr/bin/wine -> /etc/alternatives/wine -> /usr/bin/wine32

This is running q4wine v1.0-rc3, wine-1.7.2 on Debian Sid, however I've had different results between q4wine and just running from the command line before on Arch Linux (see my test-result here http://appdb.winehq.org/objectManager.php?sClass=version&iId=25607&iTestingId=70359&bShowAll=true)

[brezerk]

What then is the difference between /usr/bin/wine32 and /usr/bin/wine?

Well... It is your system. So it is only you who can answer on this question.

Your wine binary was not upgraded correctly, or you have an older one somewhere in your PATH. Or maybe the wrong wineserver is still running?

By quick look on your logs, I think that you have misconfiguration on you system:

lrwxrwxrwx 1 root root 22 Sep 2 18:04 /usr/bin/wine -> /etc/alternatives/wine -rwxr-xr-x 1 root root 1039 Oct 3 2012 /usr/bin/wine32

wine32 looks pretty old and i believe it is broken itself. for some reasons, q4wine is configured to use it's binaries and libraries (or mix of new and old files). I believe q4wine's auto detection fails is b/c your system is inconsistent.

Please, configure q4wine to use correct wine binaries and libraries manually see: http://q4wine.brezblock.org.ua/documentation/en_us/11-settings.html#general

[JKAbrams]

You are right. I had a bunch of old wine packages installed, as it turns out, Debian splits wine into multiple packages that all has to be removed when building wine from source. Sorry about the support issue, my previous problems is still unexplained, but I'm gonna assume user until I can reproduce it. This issue can be closed as invalid.

[brezerk]

I see. No problem. Feedbacks are always welcome.