5.0 kills previously working app

Questions about Wine on Linux
Locked
Vance_G
Newbie
Newbie
Posts: 4
Joined: Thu Jan 23, 2020 10:35 pm

5.0 kills previously working app

Post by Vance_G »

Running Lubuntu 16.04 LTS.

Old 16-bit customer management app I use daily stopped working when upgrading to 5.0 from 4.0.3. Doesn't even open. Using 64 or 32 bit WINEPREFIX does not make a difference. Other apps work OK. It ran OK with a 64 bit environment under 4.0.3.

Info from Terminal window:

~$ wine /home/v-green/.wine32/drive_c/SCM/SCM.EXE
*** stack smashing detected ***: C:\windows\syswow64\winevdm.exe terminated
0060:err:seh:setup_exception_record nested exception on signal stack in thread 0060 eip f776fba9 esp 7ffd3948 stack 0x1292000-0x1390000
005f:err:ntdll:RtlpWaitForCriticalSection section 0x7e83a3e0 "syslevel.c: Win16Mutex" wait timed out in thread 005f, blocked by 0060, retrying (60 sec)
005f:err:ntdll:RtlpWaitForCriticalSection section 0x7e83a3e0 "syslevel.c: Win16Mutex" wait timed out in thread 005f, blocked by 0060, retrying (60 sec)
^C0062:fixme:console:CONSOLE_DefaultHandler Terminating process 5d on event 0


(stopped timeouts with Ctrl-C).

Any thoughts? I looked into reverting to 4.0.3, but am unsure of the process. Would prefer to stay up to date with the current version if at all possible, but will do whatever is necessary.

Thanks for any help.
jkfloris
Level 12
Level 12
Posts: 3141
Joined: Thu Aug 14, 2014 10:10 am

Re: 5.0 kills previously working app

Post by jkfloris »

~$ wine /home/v-green/.wine32/drive_c/SCM/SCM.EXE
*** stack smashing detected ***: C:\windows\syswow64\winevdm.exe terminated
A 32 bit Wine prefix doesn't have a syswow64 directory. Or did you call your 64 bit prefix .wine32?
So is this a 32 or a 64 bit Wineprefix terminal output?
I looked into reverting to 4.0.3, but am unsure of the process. Would prefer to stay up to date with the current version if at all possible
You could install Wine stable 4.0.3 and Wine devel 5.0. This way you stay up to date and have an older version!
The following example set Wine devel as your default Wine installation. If you want to run the older Wine stable you
have to run: /opt/wine-stable/bin/wine program.exe

Code: Select all

# Install Wine devel 
sudo apt install --install-recommends winehq-devel
# Downgrade and hold Wine stable:
sudo apt install wine-stable=4.0.3~xenial wine-stable:i386=4.0.3~xenial wine-stable-amd64=4.0.3~xenial wine-stable-i386=4.0.3~xenial
sudo apt-mark hold wine-stable wine-stable:i386 wine-stable-amd64 wine-stable-i386
If you are sure the program works in 4.0.3 and not in 5.0, then you should write a bug report on: https://bugs.winehq.org/
Vance_G
Newbie
Newbie
Posts: 4
Joined: Thu Jan 23, 2020 10:35 pm

Re: 5.0 kills previously working app

Post by Vance_G »

Thanks for the quick response. Some questions and clarifications below:

"A 32 bit Wine prefix doesn't have a syswow64 directory. Or did you call your 64 bit prefix .wine32?

So is this a 32 or a 64 bit Wineprefix terminal output?"


I believe this is from the output from the 32 bit Wineprefix. Is it a no-no to have named it .wine32?

"The following example set Wine devel as your default Wine installation. If you want to run the older Wine stable you have to run: /opt/wine-stable/bin/wine program.exe":

In the interest of getting things to just work once more, I will forego having two versions just now.

If I want to revert my current 5.0 install to 4.0.3, would I only need to run the commands listed after "# Downgrade and hold Wine stable:" to accomplish that?

"If you are sure the program works in 4.0.3 and not in 5.0, then you should write a bug report on: https://bugs.winehq.org/"

Once I have my stuff working again, I will do this. Right now it is more important that I regain access to my customer data files.

Thanks once more for taking the time to respond.
jkfloris
Level 12
Level 12
Posts: 3141
Joined: Thu Aug 14, 2014 10:10 am

Re: 5.0 kills previously working app

Post by jkfloris »

If I want to revert my current 5.0 install to 4.0.3, would I only need to run the commands listed after "# Downgrade and hold Wine stable:" to accomplish that?
Yes, you only need:
(Note: I made a mistake in the previous reply. You don't need wine-stable:i386)

Code: Select all

sudo apt install wine-stable=4.0.3~xenial wine-stable-amd64=4.0.3~xenial wine-stable-i386=4.0.3~xenial
sudo apt-mark hold wine-stable wine-stable-amd64 wine-stable-i386
Is it a no-no to have named it .wine32?
You can name a prefix anything you want.
jkfloris
Level 12
Level 12
Posts: 3141
Joined: Thu Aug 14, 2014 10:10 am

Re: 5.0 kills previously working app

Post by jkfloris »

:oops: Probably you also have to downgrade the winehq-stable package:

Code: Select all

sudo apt install winehq-stable=4.0.3~xenial wine-stable=4.0.3~xenial wine-stable-amd64=4.0.3~xenial wine-stable-i386=4.0.3~xenial
sudo apt-mark hold wine-stable wine-stable-amd64 wine-stable-i386
Vance_G
Newbie
Newbie
Posts: 4
Joined: Thu Jan 23, 2020 10:35 pm

Re: 5.0 kills previously working app

Post by Vance_G »

And I'm back in business. Excellent and thanks much.

I have looked up the procedure for reporting this and will follow up with the devs soon. I am probably the only person in the known universe still running Skyline Contact Manager (I can't even find a reference on the internet to show you) so feel a little guilty making a case out of this, but the same problem might be affecting other users of other software so...
Locked