On Mon, 5 May 2025 21:07:11 +0300 Mikhail Krylov <sqar...@gmail.com> wrote:
On Sun, May 04, 2025 at 11:02:49PM +0000, Michael Gilbert wrote:
> Are you sure this wasn't with 10.0~rc2~repack-3? That was the first
> version built with binutils 2.44 that introduced this problem. I
> applied upstream's fix in 10.0~rc2~repack-4, which remains included in
> 10.0~repack-3.
So I've tried various versions now and can say that this problem appears
as early as 10.0rc2~repack-2. Couldn't check 10.0rc2~repack-1 or
10.0rc1~repack-1 since they are unavaliable here
http://snapshot.debian.org/package/wine/
But 9.0~repack-7 works well.
Hi, I tried reproducing this on an amd64 machine, but I don't get the
same results as your i686.
Tried these combinations successfully:
$ winecfg
$ wine winecfg
$ /usr/lib/wine/wine winecfg (the i686 executable)
Have you tested this on a fresh new wine prefix?
And are you running it on a standard debian trixie or something else -
sys info doesn't line up with trixie?
--
Regards,
Ahmad
