#1108987 wine not working in trixie

Package:
wine
Source:
wine
Submitter:
Bill Miller
Date:
2025-11-01 18:17:02 UTC
Severity:
normal
Tags:
#1108987#5
Date:
2025-07-08 22:48:39 UTC
From:
To:
Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
On trixie installed wine, added i386 arch and installed wine32:i386. Install went fine but wine won't run windows programs or winecfg. Always fails with "wine: could not load kernel32.dll, status c0000135" error



   * What exactly did you do (or not do) that was effective (or
     ineffective)?
I tried to run windows programs and winecfg
   * What was the outcome of this action?
They did not work
   * What outcome did you expect instead?
I expected them to work
*** End of the template - remove these template lines ***

#1108987#10
Date:
2025-08-06 16:53:07 UTC
From:
To:
Testing on the lastest version of trixie reveals that wine still works
if you explicitly specify the wineprefix

#1108987#15
Date:
2025-10-05 04:33:38 UTC
From:
To:
control: tag -1 moreinfo

Bill Miller wrote:

Is your default wineprefix 64-bit?  If so, wine32 will not be able to use it.

Best wishes,
Mike

#1108987#20
Date:
2025-10-05 04:33:38 UTC
From:
To:
control: tag -1 moreinfo

Bill Miller wrote:

Is your default wineprefix 64-bit?  If so, wine32 will not be able to use it.

Best wishes,
Mike

#1108987#25
Date:
2025-11-01 18:15:43 UTC
From:
To:
Bill Miller wrote:

It is possible that wine prefixes touched by releases affected by
#1104317 (a bug caused by a binutils update, wine_10.0~rc2~repack-2 to
wine_10.0~repack-5) are possibly broken.

This could explain why a clean prefix works just fine with the latest
releases, if anyone is interested in testing that hypothesis.

Best wishes,
Mike

#1108987#28
Date:
2025-11-01 18:15:43 UTC
From:
To:
Bill Miller wrote:

It is possible that wine prefixes touched by releases affected by
#1104317 (a bug caused by a binutils update, wine_10.0~rc2~repack-2 to
wine_10.0~repack-5) are possibly broken.

This could explain why a clean prefix works just fine with the latest
releases, if anyone is interested in testing that hypothesis.

Best wishes,
Mike