Caustic on Debian 9

[LMLM]

I wish I could pick up from my previous topics on this topic, but they have been locked, I have no idea why.

I just upgraded to Debian Stretch and I am trying to run Caustic again. Because there are reports of other people who run it successfully. I just tried and got this result:

[code]$ wine /home/audio/caustic/Caustic_31/app/Caustic.exe
fixme:winediag:start_process Wine Staging 2.18 is a testing version containing experimental patches.
fixme:winediag:start_process Please mention your exact version when filing bug reports on winehq.org.
fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x32fc7c 1 C) semi-stub
err:wgl:init_opengl Failed to load libGL: libGL.so.1: cannot open shared object file: No such file or directory
err:wgl:init_opengl OpenGL support is disabled.
fixme:avrt:AvSetMmThreadCharacteristicsW (L"Audio",0xb7e978): stub
fixme:avrt:AvSetMmThreadCharacteristicsW (L"Audio",0x11de978): stub
fixme:avrt:AvSetMmThreadCharacteristicsW (L"Audio",0x15ee978): stub
fixme:avrt:AvSetMmThreadCharacteristicsW (L"Audio",0x11de978): stub
fixme:avrt:AvSetMmThreadCharacteristicsW (L"Audio",0x16ee978): stub
^Cfixme:console:CONSOLE_DefaultHandler Terminating process 8 on event 0
[/code]

I do have libGL.so.1 installed, part of the libgl1-mesa-glx. Why does it not run?

Caustic is available here:
http://singlecellsoftware.com/node/5249

[Bob Wya]

Please in future user the forum Code:

Code: Select all

 Code

tags for delimiting terminal output and commands.

Presuming your on 64-bit version of Debian... Then remember the main wine process is 32-bit... So if you're using the FOSS graphics stack; you'll need the 32-bit Mesa GL libraries. Just check whether you have a 32-bit libGL.so library or symbolic link, etc present - once you've installed the 32-bit Mesa GL/ GLX library.

Bob

[LMLM]

Presuming your on 64-bit version of Debian... Then remember the main wine process is 32-bit... So if you're using the FOSS graphics stack; you'll need the 32-bit Mesa GL libraries. Just check whether you have a 32-bit libGL.so library or symbolic link, etc present - once you've installed the 32-bit Mesa GL/ GLX library.

Can you please tell me how to do that? I remember I did it in Jessie, but it was almost two years ago and I don't remember how I did it and I can't find how to do it. There isn't that option in the Synaptic repository.

[Bob Wya]

Sure... On my Ubuntu Mate 17.10 install:

Code: Select all

find /usr/ -iname "libgl.so"
/usr/lib/nvidia-384/libGL.so
/usr/lib32/nvidia-384/libGL.so

ls -hl /usr/lib32/nvidia-384/libGL.so*
lrwxrwxrwx 1 root root   10 Oct 16 10:20 /usr/lib32/nvidia-384/libGL.so -> libGL.so.1
lrwxrwxrwx 1 root root   14 Oct 16 10:20 /usr/lib32/nvidia-384/libGL.so.1 -> libGL.so.1.0.0
-rw-r--r-- 1 root root 517K Sep 20 01:44 /usr/lib32/nvidia-384/libGL.so.1.0.0

ls -hl /usr/lib/nvidia-384/libGL.so*
lrwxrwxrwx 1 root root   10 Oct 16 10:20 /usr/lib/nvidia-384/libGL.so -> libGL.so.1
lrwxrwxrwx 1 root root   14 Oct 16 10:20 /usr/lib/nvidia-384/libGL.so.1 -> libGL.so.1.0.0
-rw-r--r-- 1 root root 651K Sep 20 00:58 /usr/lib/nvidia-384/libGL.so.1.0.0

Obviously things will be different on your system - as you are using the FOSS graphics drivers.

Bob

[LMLM]

OK, thanks, but it's not working for me. According to Debian, I found the packages that contain libGL:

https://packages.debian.org/cgi-bin/sea ... earchfiles

Your local search doesn't work for me, I have to use wildcards to find it:

Code: Select all

> find /usr/ -iname "libgl.so"
> 
> find /usr/ -iname "*libgl.so*"
/usr/lib/x86_64-linux-gnu/primus/libGL.so.1
/usr/lib/x86_64-linux-gnu/libGL.so.1
/usr/lib/x86_64-linux-gnu/nvidia/current/libGL.so.1.0.0
/usr/lib/x86_64-linux-gnu/nvidia/current/libGL.so.1
/usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1
/usr/lib/x86_64-linux-gnu/nvidia/legacy-304xx/libGL.so.304.135
/usr/lib/x86_64-linux-gnu/nvidia/legacy-304xx/libGL.so.1
/usr/lib/x86_64-linux-gnu/nvidia/legacy-340xx/libGL.so.340.102
/usr/lib/x86_64-linux-gnu/nvidia/legacy-340xx/libGL.so.1
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1.2.0

I suspect I even installed more packages than I needed. But it still doesn't work:

Code: Select all

$ wine /home/audio/caustic/Caustic_31/app/Caustic.exe
fixme:winediag:start_process Wine Staging 2.18 is a testing version containing experimental patches.
fixme:winediag:start_process Please mention your exact version when filing bug reports on winehq.org.
err:wgl:init_opengl Failed to load libGL: libGL.so.1: cannot open shared object file: No such file or directory
err:wgl:init_opengl OpenGL support is disabled.
fixme:avrt:AvSetMmThreadCharacteristicsW (L"Audio",0xb7e978): stub
fixme:avrt:AvSetMmThreadCharacteristicsW (L"Audio",0x11de978): stub
fixme:avrt:AvSetMmThreadCharacteristicsW (L"Audio",0x15ee978): stub
fixme:avrt:AvSetMmThreadCharacteristicsW (L"Audio",0x11de978): stub
fixme:avrt:AvSetMmThreadCharacteristicsW (L"Audio",0x16ee978): stub
^Cfixme:console:CONSOLE_DefaultHandler Terminating process 8 on event 0

Note that I had to kill it (^C) after a while, because wine hangs.

What else can I do?

[Bob Wya]

OK, thanks, but it's not working for me. According to Debian, I found the packages that contain libGL:

https://packages.debian.org/cgi-bin/sea ... earchfiles

Your local search doesn't work for me, I have to use wildcards to find it:

Code: Select all

> find /usr/ -iname "libgl.so"
> 
> find /usr/ -iname "*libgl.so*"
/usr/lib/x86_64-linux-gnu/primus/libGL.so.1
/usr/lib/x86_64-linux-gnu/libGL.so.1
/usr/lib/x86_64-linux-gnu/nvidia/current/libGL.so.1.0.0
/usr/lib/x86_64-linux-gnu/nvidia/current/libGL.so.1
/usr/lib/x86_64-linux-gnu/nvidia/libGL.so.1
/usr/lib/x86_64-linux-gnu/nvidia/legacy-304xx/libGL.so.304.135
/usr/lib/x86_64-linux-gnu/nvidia/legacy-304xx/libGL.so.1
/usr/lib/x86_64-linux-gnu/nvidia/legacy-340xx/libGL.so.340.102
/usr/lib/x86_64-linux-gnu/nvidia/legacy-340xx/libGL.so.1
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1.2.0

I suspect I even installed more packages than I needed. But it still doesn't work:
...
What else can I do?

My package search, above, with the wildcard addition, is only showing 64-bit GL libraries.
Where, pray tell, are your 32-bit GL libraries?!!

It's no wonder your application is still not working under Wine...

Bob

[LMLM]

Well, that was my question in reply to your first reply: how do I install 32bit libraries on a 64bit system? Synaptic doesn't give me that option.

[Bob Wya]

Well, that was my question in reply to your first reply: how do I install 32bit libraries on a 64bit system? Synaptic doesn't give me that option.

I believe Debian uses a multiarch setup similar to Ubuntu's. See: Debian Wiki: Multiarch HOWTO ...

Bob

[LMLM]

I think I found a way, the libraries were installed, but it still doesn't work:

Code: Select all

> find /usr/ -iname "*libgl.so*"
/usr/lib/x86_64-linux-gnu/primus/libGL.so.1
/usr/lib/x86_64-linux-gnu/nvidia/legacy-304xx/libGL.so.304.135
/usr/lib/x86_64-linux-gnu/nvidia/legacy-304xx/libGL.so.1
/usr/lib/x86_64-linux-gnu/nvidia/legacy-340xx/libGL.so.340.102
/usr/lib/x86_64-linux-gnu/nvidia/legacy-340xx/libGL.so.1
/usr/lib/i386-linux-gnu/nvidia/current/libGL.so.375.82
/usr/lib/i386-linux-gnu/nvidia/current/libGL.so.1
/usr/lib/i386-linux-gnu/nvidia/libGL.so.1
/usr/lib/i386-linux-gnu/libGL.so.1
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1.2.0
/usr/lib/mesa-diverted/i386-linux-gnu/libGL.so.1
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1.2.0

> wine /home/audio/caustic/Caustic_31/app/Caustic.exe
fixme:winediag:start_process Wine Staging 2.18 is a testing version containing experimental patches.
fixme:winediag:start_process Please mention your exact version when filing bug reports on winehq.org.
X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  155 (GLX)
  Minor opcode of failed request:  3 (X_GLXCreateContext)
  Value in failed request:  0x0
  Serial number of failed request:  169
  Current serial number in output stream:  170

And I had problems:

Code: Select all

The following packages will be REMOVED:
  libgl1-glvnd-nvidia-glx libgl1-nvidia-glvnd-glx
The following NEW packages will be installed:
  libgl1-nvidia-glx:i386 libnvidia-glcore:i386

So wine would no longer complain about the lack of libGL.so.1, but then mplayer wouldn't work anymore. I know because it plays notifications on my system, and I tried to play a video and confirmed that it broke.

So I rolled back the changes and wine complains about libGL.so.1 again.

[Bob Wya]

...

So wine would no longer complain about the lack of libGL.so.1, but then mplayer wouldn't work anymore. I know because it plays notifications on my system, and I tried to play a video and confirmed that it broke.

So I rolled back the changes and wine complains about libGL.so.1 again.

Heh, heh... I think this is the point when I say - "that's why I use Gentoo ... "

My understanding of Debian Multiarch - is pretty limited - to say the least.
But I do know you want to use aptitude to install stuff - not apt (the latter will quick happily bork your system completely).

Always safest to ask about this sort of thing on the /r/debian subreddit or the Debian User Forums ...

Btw, since you've not even hinted what your graphics hardware is, what's the output from:

Code: Select all

glxinfo | egrep 'direct |version[ :]'
sudo lspci -v | awk '{ if ($0 ~ "VGA") glx_open=1; else if ($0 ~ "^[[:blank:]]*$") glx_open=0; if (glx_open) print $0 }'

Just to check you actually want to install the Nvidia Proprietary driver in the first place...

Ta
Bob

[LMLM]

Code: Select all

#> glxinfo | egrep 'direct |version[ :]'
X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  155 (GLX)
  Minor opcode of failed request:  24 (X_GLXCreateNewContext)
  Value in failed request:  0x0
  Serial number of failed request:  38
  Current serial number in output stream:  39
#> glxinfo 
name of display: :0
X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  155 (GLX)
  Minor opcode of failed request:  24 (X_GLXCreateNewContext)
  Value in failed request:  0x0
  Serial number of failed request:  38
  Current serial number in output stream:  39

Code: Select all

#> lspci -v | awk '{ if ($0 ~ "VGA") glx_open=1; else if ($0 ~ "^[[:blank:]]*$") glx_open=0; if (glx_open) print $0 }'
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller])
        Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller
        Flags: bus master, fast devsel, latency 0, IRQ 27
        Memory at f7800000 (64-bit, non-prefetchable) [size=4M]
        Memory at e0000000 (64-bit, prefetchable) [size=256M]
        I/O ports at f000 [size=64]
        [virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
        Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
        Capabilities: [d0] Power Management version 2
        Capabilities: [a4] PCI Advanced Features
        Kernel driver in use: i915
        Kernel modules: i915

[Bob Wya]

Code: Select all

#> glxinfo | egrep 'direct |version[ :]'
X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  155 (GLX)
  Minor opcode of failed request:  24 (X_GLXCreateNewContext)
  Value in failed request:  0x0
  Serial number of failed request:  38
  Current serial number in output stream:  39
#> glxinfo 
name of display: :0
X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  155 (GLX)
  Minor opcode of failed request:  24 (X_GLXCreateNewContext)
  Value in failed request:  0x0
  Serial number of failed request:  38
  Current serial number in output stream:  39

...

This is a problem... You need to fix your native Linux graphics stack - before trying to run any applications under Wine...

Bob

[LMLM]

What is a problem, why does it need to be fixed, and how do I fix it?

[LMLM]

OK, I fixes it, but still...

Code: Select all

#> glxinfo | egrep 'direct |version[ :]'
direct rendering: Yes
server glx version string: 1.4
client glx version string: 1.4
GLX version: 1.4
    Max core profile version: 3.3
    Max compat profile version: 3.0
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.0
OpenGL core profile version string: 3.3 (Core Profile) Mesa 13.0.6
OpenGL core profile shading language version string: 3.30
OpenGL version string: 3.0 Mesa 13.0.6
OpenGL shading language version string: 1.30
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 13.0.6
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00

Code: Select all

> wine /home/audio/caustic/Caustic_31/app/Caustic.exe
fixme:winediag:start_process Wine Staging 2.18 is a testing version containing experimental patches.
fixme:winediag:start_process Please mention your exact version when filing bug reports on winehq.org.
libGL error: unable to load driver: i965_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: i965
libGL error: unable to load driver: i965_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: i965
libGL error: unable to load driver: swrast_dri.so
libGL error: failed to load driver: swrast
X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  155 (GLX)
  Minor opcode of failed request:  3 (X_GLXCreateContext)
  Value in failed request:  0x0
  Serial number of failed request:  188
  Current serial number in output stream:  192

> wine: Unhandled page fault on execute access to 0x7fe2535a9510 at address 0x7fe2535a9510 (thread 0030), starting debugger...

^c

[LMLM]

Eh, some major progress made here!

I was trying to run Caustic 3.1, which was good enough.

Then I had some problems and had to reinstall Debian 9 from scratch. It cost me a lot of time, but it was worth it because there were several problems and I could "feel" that it wasn't a good vintage. Everything was kind of slow and jerky. I can tell they changed something meanwhile, because I used to have to hunt for some pesky dependencies to install some (Linux native) photography/image editing applications, and suddenly that almost wasn't needed anymore. Also, wine-staging refused to install at first due to some dependency conflicts, then I tried again the next day and it installed smoothly.

Anyway, Caustic 3.1 is running fine now! Woo-hoo! Amazing. I don't know how that happened, I didn't even have to tweak anything, it just works.

Then I thought I'd try my luck at Caustic 3.2. Well, it runs and plays the demo/intro track, but the GUI is just a big black rectangle. Caustic 3.1 is fine by me, but 3.2 would bring me more features. Is there any hope?

Code: Select all

> wine /home/audio/caustic/Caustic_3.2.0_standaloneXP/app/Caustic.exe 
fixme:winediag:start_process Wine Staging 2.19 is a testing version containing experimental patches.
fixme:winediag:start_process Please mention your exact version when filing bug reports on winehq.org.
fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x33fd30 1 C) semi-stub
fixme:avrt:AvSetMmThreadCharacteristicsW (L"Audio",0xc1e978): stub
fixme:avrt:AvSetMmThreadCharacteristicsW (L"Audio",0x152e978): stub
fixme:avrt:AvSetMmThreadCharacteristicsW (L"Audio",0x190e978): stub
fixme:avrt:AvSetMmThreadCharacteristicsW (L"Audio",0x152e978): stub
fixme:avrt:AvSetMmThreadCharacteristicsW (L"Audio",0x1aee978): stub
err:wgl:glxdrv_wglShareLists Recreating OpenGL context to share display lists, although the context has been current!
fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x33f664 1 C) semi-stub
fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x33f0dc 1 C) semi-stub
fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x33f18c 1 C) semi-stub
fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x33ef6c 1 C) semi-stub
^Cfixme:console:CONSOLE_DefaultHandler Terminating process 8 on event 0

> wine /home/audio/caustic/Caustic_3.2.0_standalone_Windows-7-8-10/app/Caustic.exe 
fixme:winediag:start_process Wine Staging 2.19 is a testing version containing experimental patches.
fixme:winediag:start_process Please mention your exact version when filing bug reports on winehq.org.
fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x33fd30 1 C) semi-stub
fixme:avrt:AvSetMmThreadCharacteristicsW (L"Audio",0xc2e978): stub
fixme:avrt:AvSetMmThreadCharacteristicsW (L"Audio",0x153e978): stub
fixme:avrt:AvSetMmThreadCharacteristicsW (L"Audio",0x191e978): stub
fixme:avrt:AvSetMmThreadCharacteristicsW (L"Audio",0x153e978): stub
fixme:avrt:AvSetMmThreadCharacteristicsW (L"Audio",0x1afe978): stub
err:wgl:glxdrv_wglShareLists Recreating OpenGL context to share display lists, although the context has been current!
fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x33f664 1 C) semi-stub
fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x33f0dc 1 C) semi-stub
fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x33f18c 1 C) semi-stub
fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x33ef6c 1 C) semi-stub
fixme:console:CONSOLE_DefaultHandler Terminating process 8 on event 0

[Bob Wya]

...

Code: Select all

> wine /home/audio/caustic/Caustic_3.2.0_standaloneXP/app/Caustic.exe 
...

...

Are you testing the legacy XP version, of your application, in a 32-bit WINEPREFIX, set to Windows XP compatibility?

I can get the stand-alone version of Caustic 3.2.0 to run (well without a black start up screen anyway) with this process:

Code: Select all

wine --version
wine-2.19             # Wine Staging 2.19 does not work

cd "${HOME}"
export WINEPREFIX="${PWD}/caustic_xp_32"
export WINEARCH=win32
wineboot -u
winetricks sandbox # <---- recommended to stop your Linux home directory getting spammed with Wine crap!
winetricks winxp    # Switch to Windows XP
cp ~/Downloads/Caustic_3.2.0_standaloneXP.zip "${WINEPREFIX}/drive_c"
cd "${WINEPREFIX}/drive_c/Program Files"
unzip ../Caustic_3.2.0_standaloneXP.zip
cd "${WINEPREFIX}/drive_c/Program Files/Caustic_3.2.0_standaloneXP/app"
wine Caustic.exe

Wine Staging version 2.19 leads to a black screen... You need to use Wine Development version 2.19.
I'll file a bug against Wine Staging - it's probably one of those rare Staging regressions!

Note
it's recommended to start your application with:

Code: Select all

wine start /unix '/home/audio/caustic/Caustic_3.2.0_standaloneXP/app/Caustic.exe'

if you're going to use a full Unix-style path. Not doing this can cause random breakage - e.g. if bundled dll libraries are stored in the application directory:

Code: Select all

/home/audio/caustic/Caustic_3.2.0_standaloneXP/app/

See: Wine User's Guide: 3 Using Wine ...

Bob

[Bob Wya]

WineHQ Bug filed: Bug 43921 - Caustic 3.2.0 (standalone) black/blank UI with Wine Staging ; functional UI with Wine Development ...

[LMLM]

Thank you for that, plus all the attention. You have just provided me with a sizeable amount of new information and it's Monday, i.e. I am back to work and not very free, so I'll need some time to digest all of this. I will be back if I have other questions.

Thank you very much.

[Bob Wya]

np