[Bug 47297] New: Upgrading wine 4.8 on Fedora in 5.0.9-200.FC29 broke me

https://bugs.winehq.org/show_bug.cgi?id=47297

Bug ID: 47297
           Summary: Upgrading wine 4.8 on Fedora in 5.0.9-200.FC29 broke
                    me
           Product: Packaging
           Version: unspecified
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: P2
         Component: wine-packages
          Assignee: [e-mail]
          Reporter: [e-mail]
                CC: [e-mail], [e-mail],
                    [e-mail]
      Distribution: ---

Description of problem: Upgrading from 5.0.9-200.FC29 to 5.0.17.FC29 a windows
program running under WINE ( Wine Staging 4.8 ) no longer works.  Been using
this program for years under WINE without problems before the upgrade

Tried 32bit applications - they work

All 64bit applications fail

attempted to downgrade to v4.7, but it seems this is not on the repository
When i select the downgrade option, all files are v3.16. Unable to select v4.71
as previous version before 25/05/2019. dnf --showduplicates list wine lists the
same versions, 4.8 and 3.16

Tried to downgrade, but not able to - as downgrade works for others

dnf install mingw64-qt5-qtwinextras

After 0.5GByte of files installed, still does not work

[Bug 47297] Upgrading wine 4.8 on Fedora in 5.0.9-200.FC29 broke me

https://bugs.winehq.org/show_bug.cgi?id=47297

--- Comment #1 from Rosanne DiMesio  ---
(In reply to JD Delancy from comment #0)
> Description of problem: Upgrading from 5.0.9-200.FC29 to 5.0.17.FC29 a
> windows program running under WINE ( Wine Staging 4.8 ) no longer works.

So you upgraded your kernel, and an existing wineprefix no longer works? That's
not a Wine packaging bug.
> attempted to downgrade to v4.7, but it seems this is not on the repository

4.7 is definitely in the WineHQ repository. Are you using the distro Wine
packages or the WineHQ packages?

[Bug 47297] Upgrading wine 4.8 on Fedora in 5.0.9-200.FC29 broke me

https://bugs.winehq.org/show_bug.cgi?id=47297

Shadders  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |richard.shadbolt@btinternet
                   |                            |.com

--- Comment #2 from Shadders  ---
Hi,
Not sure how this should be progressed - for myself, it was the upgrade to wine
staging 4.8 that caused the issue. I have used PlayOnLinux and all virtual
drives are wine 4.7, and this functions.

I used a previous kernel - same issue, so it is not a kernel issue.

Whether 4.7, or 4.8 is on the WineHQ servers etc., is not the issue, v4.8
staging fails for 64bit applications.

If you wish to test - then LTSpiceXVII is the program that fails for myself :
https://www.analog.com/en/design-center/design-tools-and-calculators/ltspice...

The program will fail to start. I am using Fedora 29, kernel 5.0.17, and tested
on 5.0.16 - both fail.

Regards,
Shadders.

[Bug 47297] Upgrading wine 4.8 on Fedora in 5.0.9-200.FC29 broke me

https://bugs.winehq.org/show_bug.cgi?id=47297

--- Comment #3 from Shadders  ---
Hi,
I have implemented the application LTSpiceXVII 64bit on PlayOnLinux with v4.8
staging, and it fails to run :

=======================================
[05/30/19 11:19:10] - Running wine-4.8-staging XVIIx64.exe (Working directory :
/home/richard/.PlayOnLinux/wineprefix/LTSpiceXVII_Stage4.8/drive_c/Program
Files/LTC/LTspiceXVII)
000b:fixme:winediag:start_process Wine Staging 4.8 is a testing version
containing experimental patches.
000b:fixme:winediag:start_process Please mention your exact version when filing
bug reports on winehq.org.
=======================================

The versions of Wine for PlayOnLinux were downloaded from the PlayOnLinux
servers, not the WineHQ repository.

Regards,
Shadders.

[Bug 47297] Upgrading wine 4.8 on Fedora in 5.0.9-200.FC29 broke me

https://bugs.winehq.org/show_bug.cgi?id=47297

Rosanne DiMesio  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |NEEDINFO

--- Comment #4 from Rosanne DiMesio  ---
This was filed as a packaging bug, so if the OR is not using the WineHQ
packages, this bug is invalid. "Wine-packaging" is for bugs that exist only in
the WineHQ packages and are the result of something in our packaging process.

[Bug 47297] Upgrading wine 4.8 on Fedora in 5.0.9-200.FC29 broke me

https://bugs.winehq.org/show_bug.cgi?id=47297

--- Comment #5 from Shadders  ---
Hi,
Can you change it to Wine-Staging - this would seem to be more appropriate.

Regards,
Shadders.

[Bug 47297] Upgrading wine 4.8 on Fedora in 5.0.9-200.FC29 broke me

https://bugs.winehq.org/show_bug.cgi?id=47297

--- Comment #6 from Rosanne DiMesio  ---
(In reply to Shadders from comment #5)
> Can you change it to Wine-Staging - this would seem to be more appropriate.

I'm not going to change the anything without hearing from the OR. We don't even
know what app he or she was trying to run; the problem could be unrelated to
yours.

FYI, I downloaded LTSpice from the link you posted and it starts and runs
perfectly fine for me in plain wine-4.9 (development, not staging). This may be
a problem that is already solved in current Wine, it may as you suggest be a
problem specific to wine-staging, it may be a problem specific to Fedora (I'm
on openSUSE), or it may be a problem caused by your using PoL, which is not
supported here. What I recommend you do is test it yourself in plain Wine 4.9
(no PoL or other third party modifications) and if the problem is still present
for you, run a regression test and file a bug for your specific problem.

[Bug 47297] Upgrading wine 4.8 on Fedora in 5.0.9-200.FC29 broke me

https://bugs.winehq.org/show_bug.cgi?id=47297

--- Comment #7 from Shadders  ---
Hi,
Yes - i have just downloaded wine 4.9 (not staging) using PlayOnLinux and run
the LTSpice application and it runs.

To summarise :
LTSpiceXVII works on Wine 4.7 Staging
LTSpiceXVII works on Wine 4.8
LTSpiceXVII works on Wine 4.9
LTSpiceXVII does not work on Wine 4.8 Staging

Regards,
Shadders.

[Bug 47297] Upgrading wine 4.8 on Fedora in 5.0.9-200.FC29 broke me

https://bugs.winehq.org/show_bug.cgi?id=47297

--- Comment #8 from Shadders  ---
Hi,
I forgot to add - 25th May 2019 the distribution upgraded to v4.8 staging which
failed, and all previous versions worked no issue.

I understand you want to remove any intermediate process such as PoL, but i do
think this is sufficient evidence (including previous comment) of v4.8 staging
having an issue.

Regards,
Shadders.

[Bug 47297] Upgrading wine 4.8 on Fedora in 5.0.9-200.FC29 broke me

https://bugs.winehq.org/show_bug.cgi?id=47297

--- Comment #9 from Rosanne DiMesio  ---
You haven't tested 4.9 staging; you need to. If the problem is still present in
4.9 staging, please run a regression test and file a bug.

[Bug 47297] Upgrading wine 4.8 on Fedora in 5.0.9-200.FC29 broke me

https://bugs.winehq.org/show_bug.cgi?id=47297

--- Comment #10 from Shadders  ---
Hi,
OK - i do not have access to 4.9 staging on PoL, nor the Fedora repository. I
want to keep my deployment synchronised with the Fedora servers.

All i can provide using the current Fedora 29 build is that v4.8 staging fails
to work with LTSpiceXVII x64, as replicated on PoL. All other wine versions
function as per PoL downloads, and Fedora packaged v4.7 and earlier Wine
versions.

Regards,
Shadders.

[Bug 47297] Upgrading wine 4.8 on Fedora in 5.0.9-200.FC29 broke me

https://bugs.winehq.org/show_bug.cgi?id=47297

Rosanne DiMesio  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |WORKSFORME
             Status|NEEDINFO                    |RESOLVED

--- Comment #11 from Rosanne DiMesio  ---
Packages for winehq-staging-4.9 have been in the WineHQ repository since May
26.

I tested the winehq-staging-4.9 packages myself in a Fedora 29 VM, and 64 bit
LTSpiceXVII works perfectly fine.

Marking WORKSFORME.

[Bug 47297] Upgrading wine 4.8 on Fedora in 5.0.9-200.FC29 broke me

https://bugs.winehq.org/show_bug.cgi?id=47297

Rosanne DiMesio  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #12 from Rosanne DiMesio  ---
Closing packaging bug.

[Bug 47297] Upgrading wine 4.8 on Fedora in 5.0.9-200.FC29 broke me

https://bugs.winehq.org/show_bug.cgi?id=47297

--- Comment #13 from Shadders  ---
(In reply to Rosanne DiMesio from comment #11)
> Packages for winehq-staging-4.9 have been in the WineHQ repository since May
> 26.
>
> I tested the winehq-staging-4.9 packages myself in a Fedora 29 VM, and 64
> bit LTSpiceXVII works perfectly fine.
>
> Marking WORKSFORME.

Hi,
Bug relates to v4.8 staging, not v4.9 staging. This is the same for JD Delancy. 
Regards,
Shadders.