https://bugs.winehq.org/show_bug.cgi?id=51396
Bug ID: 51396
Summary: cl.exe sometimes fails with internal compiler error
Product: Wine
Version: 6.12
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: rpisl(a)seznam.cz
Distribution: ---
Cl.exe from MSVC 2019 Build Tools sometimes fails with: "fatal error C1001:
Internal compiler error." A workaround is setting vcruntime140_1 to native.
This is possibly caused by unsupported flag in __CxxFrameHandler4:
0b24:fixme:seh:__CxxFrameHandler4 unsupported flags: 7a
which is unsupported FUNC_DESCR_IS_SEPARATED in
dlls/vcruntime140_1/except_x86_64.c
Not critical since the workaround exists. I'm ready to test this when the flag
is implemented.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51195
Bug ID: 51195
Summary: Lara Croft and the Temple of Osiris doesn't launch
Product: Wine
Version: 6.9
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
Distribution: ---
Created attachment 70069
--> https://bugs.winehq.org/attachment.cgi?id=70069
log
d3dcompiler_43 - native,builtin
d3dx11_43 - native,builtin
(Otherwise the game fails after hitting 'Play' with "Failed to initialize
Direct3D with current settings")
msvcr110 - native,builtin (for launcher) Bug 49541
Assertion failed: iface->lpVtbl == &d3d11_rendertarget_view_vtbl, file
../wine/dlls/d3d11/view.c, line 1794
04d4:warn:d3d11:d3d_rendertarget_view_init Failed to create a wined3d
rendertarget view, hr 0x80070057.
04d4:warn:d3d11:d3d_rendertarget_view_create Failed to initialize rendertarget
view, hr 0x80070057.
wine-6.9-148-gce151dd681f
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50714
Bug ID: 50714
Summary: CMS client stopped working after latest wine update
Product: Wine
Version: 6.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: denis.salmanovich(a)gmail.com
Distribution: ---
Created attachment 69460
--> https://bugs.winehq.org/attachment.cgi?id=69460
errors backtrace
Hello,
I am using version 5.9 of wine and CMS client
(https://camerayoosee.com/yoosee-cap-nhat-phien-ban-phan-mem-cms-client-moi-…)
version 1.0.0.53 and it works fine.
But if I want to update wine version to latest/newer (5.12 or 6.1) - I get
error after login screen. Tried on two different machines with different
kernels (both stack traces attached).
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=48631
Bug ID: 48631
Summary: Death to Spies: Moment of Truth demo renders text as a
black squares
Product: Wine
Version: 5.2
Hardware: x86-64
URL: http://files.aspyr.com/support/DTS_Demo_Installer.zip
OS: Linux
Status: NEW
Keywords: download
Severity: minor
Priority: P2
Component: directx-d3dx9
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
Distribution: ---
Created attachment 66482
--> https://bugs.winehq.org/attachment.cgi?id=66482
screenshot
Setting d3dx9_32 to 'native,builtin' helps.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51978
Bug ID: 51978
Summary: Autodesk fusion360 crashes at start: wine: Call from
000000007B01231E to unimplemented function
msvcp140.dll.?table@?$ctype@D@std@@QEBAPEBFXZ,
aborting
Product: Wine
Version: 6.19
Hardware: x86-64
URL: "https://dl.appstreaming.autodesk.com/production/insta
llers/Fusion%20360%20Admin%20Install.exe"
OS: Linux
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: msvcp
Assignee: wine-bugs(a)winehq.org
Reporter: xerox.xerox2000x(a)gmail.com
Distribution: Debian
Hi, as the title says
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51860
Bug ID: 51860
Summary: Missing include for uid_t on musl-based systems
Product: Wine
Version: 6.19
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wineserver
Assignee: wine-bugs(a)winehq.org
Reporter: ismael(a)iodev.co.uk
Distribution: ---
Build log:
gcc -m64 -c -o server/event.o server/event.c -Iserver -Iinclude -D__WINESRC__
-Wall -pipe -fcf-protection=none \
-fno-stack-protector -fno-strict-aliasing -Wdeclaration-after-statement
-Wempty-body \
-Wignored-qualifiers -Winit-self -Wno-packed-not-aligned -Wshift-overflow=2
-Wstrict-prototypes \
-Wtype-limits -Wunused-but-set-parameter -Wvla -Wwrite-strings
-Wpointer-arith -Wlogical-op \
-march=native -mtune=native -m64 -pipe -fPIC -ffast-math -funroll-loops -Os
In file included from server/object.h:25,
from server/thread.h:24,
from server/event.c:34:
/usr/include/sys/poll.h:1:2: warning: #warning redirecting incorrect #include
<sys/poll.h> to <poll.h> [-Wcpp]
1 | #warning redirecting incorrect #include <sys/poll.h> to <poll.h>
| ^~~~~~~
In file included from server/event.c:36:
server/security.h:89:45: error: unknown type name 'uid_t'; did you mean
'luid_t'?
89 | extern const SID *security_unix_uid_to_sid( uid_t uid );
| ^~~~~
| luid_t
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=48950
Bug ID: 48950
Summary: NVDA requires AccessibleObjectFromPoint for mouse
tracking
Product: Wine
Version: 5.6
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: oleacc
Assignee: wine-bugs(a)winehq.org
Reporter: contact(a)jookia.org
Distribution: ArchLinux
In order to track the mouse pointer and read what's under the mouse NVDA tries
to get an IAccessible object using AccessibleObjectFromPoint. This fails with a
stub and mouse tracking doesn't work.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51598
Bug ID: 51598
Summary: cmd.exe crashes on "if exist" without arguments
Product: Wine
Version: 6.14
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: programs
Assignee: wine-bugs(a)winehq.org
Reporter: alexhenrie24(a)gmail.com
Distribution: ---
Created attachment 70448
--> https://bugs.winehq.org/attachment.cgi?id=70448
Example batch file
Run `wine if-exist.bat` and a crash dialog will appear.
`wine cmd /k if exist` and `wine if-exist.bat | tee /dev/null` do not open a
crash dialog, but they do print "stack overflow" and exit.
Strangely, `wine cmd /k if-exist.bat` does NOT crash.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=41098
Bug ID: 41098
Summary: Descent 3 (GOG version) has problem when running with
OpenGL renderer (Nvidia proprietary drivers)
Product: Wine
Version: 1.7.55
Hardware: x86
OS: Linux
Status: NEW
Keywords: regression
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: gyebro69(a)gmail.com
CC: hverbeet(a)gmail.com
Regression SHA1: c92451f295242110bf016facf0e80564f3643d94
Distribution: ---
The bug reported here occurs with Nvidia binary drivers 367.35, but can't
reproduce it with nouveau/mesa.
I tried the official demo version, but it just hangs with a black screen with
the OpenGL renderer (unrelated to this regression, occurs with nouveau as well
and with older Wine versions).
When OpenGL renderer is selected in the launcher, the game starts and plays the
intro video, then the game quits after displaying this error message: 'Error:
Generic renderer error."
The OpenGL renderer in Descent 3 used to work until
commit c92451f295242110bf016facf0e80564f3643d94
Author: Henri Verbeet <hverbeet(a)codeweavers.com>
Date: Wed Nov 4 00:02:48 2015 +0100
wined3d: Always use the same formats in context_create() when
"always_offscreen" is enabled.
Disabling "AlwaysOffScreen" in the registry works around the problem.
Terminal output shows only
fixme:win:EnumDisplayDevicesW ((null),0,0x33f0d8,0x00000000), stub!
fixme:x11drv:X11DRV_desktop_SetCurrentMode Cannot change screen BPP from 32 to
16
fixme:x11drv:X11DRV_desktop_SetCurrentMode Cannot change screen BPP from 32 to
16
fixme:x11drv:X11DRV_desktop_SetCurrentMode Cannot change screen BPP from 32 to
16
Wine 1.9.16
Fedora 24
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GT 730/PCIe/SSE2
OpenGL core profile version string: 4.5.0 NVIDIA 367.35
OpenGL core profile shading language version string: 4.50 NVIDIA
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51959
Bug ID: 51959
Summary: Missing procedure GetDayLightFlag
Product: Wine
Version: 6.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ucrtbase
Assignee: wine-bugs(a)winehq.org
Reporter: deridiot(a)gmail.com
Distribution: ---
Created attachment 70942
--> https://bugs.winehq.org/attachment.cgi?id=70942
german Error Message about the missing procedure
In the build process of a python project we employ a docker image that uses
pyinstaller via wine (https://github.com/cdrx/docker-pyinstaller).
When executing the frozen exe it will raise an error noting that ucrtbase.dll
misses the procedure GetDayLightFlag
If i explicitly tell the build process to ignore ucrtbase.dll from being
included in the package it will use the dll of the system it runs on. Meaning
it doesn't employ the file supplied by wine.
I poked around the code a bit and probably we are just lacking
stdcall GetDaylightFlag()
in
https://github.com/wine-mirror/wine/blob/master/dlls/ucrtbase/ucrtbase.spec
But C isn't my language of choice so i will gladly admit that's just guessing.
I've managed to work around my problem by just excluding the dll, but i feel
this might help someone else in the future.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51864
Bug ID: 51864
Summary: VeraCrypt Installer for 1.24-Update7 (Win8+) fails
with HRESULT 0x800288BD
Product: Wine
Version: 6.18
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: oleaut32
Assignee: wine-bugs(a)winehq.org
Reporter: besentv(a)gmail.com
Distribution: ---
Created attachment 70779
--> https://bugs.winehq.org/attachment.cgi?id=70779
Veracrypt installer Winedump
Seems like the installer, a 32bit App, tries to register a 64bit TypeLib, but
it fails:
...
0100:Call oleaut32.RegisterTypeLib(00f2d118,051dd278 L"C:\\Program
Files\\VeraCrypt\\VeraCrypt.exe",00000000) ret=00403782
0100:Ret oleaut32.RegisterTypeLib() retval=800288bd ret=00403782
...
0100:Call oleaut32.RegisterTypeLib(00f2d118,051dd278 L"C:\\Program
Files\\VeraCrypt\\VeraCrypt.exe",00000000) ret=00403782
0100:Ret oleaut32.RegisterTypeLib() retval=800288bd ret=00403782
...
A quick check of the source code shows us, that wine does this on purpose:
oleaut32.typelib.c:
HRESULT WINAPI RegisterTypeLib(ITypeLib *ptlib, const WCHAR *szFullPath, const
WCHAR *szHelpDir)
{
...
#ifndef _WIN64
if (attr->syskind == SYS_WIN64) return TYPE_E_BADMODULEKIND;
#endif
...
}
Windows allows this behavior, as the installer works perfectly fine there.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=26350
Summary: Dungeons demo doesn't run
Product: Wine
Version: 1.3.15
Platform: x86
URL: http://www.bigdownload.com/games/dungeons/pc/dungeons-
demo/
OS/Version: Linux
Status: NEW
Keywords: dotnet, download
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: austinenglish(a)gmail.com
If I use mono-2.10-1, it fails with an error that mono can't handle it:
Method '<Module>:<CrtImplementationDetails>.DoDllLanguageSupportValidation ()'
in assembly 'C:\Program Files\Kalypso Media\Dungeons Demo\Mogre.dll' contains
native code that cannot be executed by Mono in modules loaded from byte arrays.
The assembly was probably created using C++/CLI.
Method '<Module>:<CrtImplementationDetails>.ThrowModuleLoadException
(string,System.Exception)' in assembly 'C:\Program Files\Kalypso Media\Dungeons
Demo\Mogre.dll' contains native code that cannot be executed by Mono in modules
loaded from byte arrays. The assembly was probably created using C++/CLI.
System.NullReferenceException: Object reference not set to an instance of an
object
With dotnet35, fails with:
Unhandled Exception: System.MissingMethodException: Method not found: 'Void
System.Runtime.GCSettings.set_LatencyMode(System.Runtime.GCLatencyMode)'.
at Realmforge.MogreUtil.Application.MainApplication`3.Run()
at Realmforge.Dungeons.DungeonsMain.Main(String[] args)
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=39699
Bug ID: 39699
Summary: WINE Crashed during setup of 'EDT for Windows'
Product: Wine
Version: 1.6-rc2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: D.Kurtz(a)web.de
Distribution: ---
Created attachment 52941
--> https://bugs.winehq.org/attachment.cgi?id=52941
Saved Crashfile
During running the Setup-Programm WINE crashed.
I have Linux-Mint 17.2 and Wine !:1.6.2 You can get the Programm 'EDTW = EDT
für Windows' at this Link: http://opg.de/download/edtw/setupedt.exe
If possible please answer in German language because my english is very bad.
Thanks
Dietmar
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52037
Bug ID: 52037
Summary: MaiDenSnow Eve trial crashes upon entering load menu
Product: Wine
Version: 6.19
Hardware: x86-64
URL: https://trial.dlsite.com/doujin/RJ116000/RJ115762_tria
l.zip
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: galtgendo(a)o2.pl
Distribution: ---
I'm reporting against 6.19, but IIRC this predates 6.0.
I have no proof that the problem stems from the code in win32u/gdiobj.c, as gdb
backtraces report stack being corrupted. Yet after changing the warning in
handle_entry to print handle value, I can see the handle (font) being accessed
after being freed by free_gdi_handle. Also, 'all,-heap' somehow sidesteps the
crash, for a price of a major slowdown. The crash is 'illegal instruction', so
once again, stack corruption.
To reproduce:
- run the trial
- pick the last option (fourth) in the menu
- pick 'New Game'
- go with the first option in the next menu
- as the game starts, access menu (press X) and save (first option)
- press F12 to quickly restart the game
- back at the title screen pick 'Load Game'
- ...get the crash
(if at any point you get a splash screen with some text and a clock image, you
need to press 'up,left,up,down,right' on the keyboard)
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=19841
Summary: Wolfenstein (2009): mouse cursor remains onscreen
during FPS gameplay even after all menus are closed.
Product: Wine
Version: 1.1.28
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: ben.r.xiao(a)gmail.com
In Wolfenstein (2009), browsing the intelligence reports or upgrading weapons
sometimes causes the mouse cursor to remain on screen even when the in-game
menus are closed. In other words, during FPS gameplay, the cursor sits right
where the crosshairs should be and does not disappear. Needless to say this is
quite distracting. This cursor bug seems to appear randomly, but always after
browsing an intelligence report or upgrading weapons. The only way to get rid
of the cursor is to restart the game. I'll post an attachment showing this bug
the next time I see it.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=46936
Bug ID: 46936
Summary: cannot upgrade to wine-devel 4.5~bionic (libfaudio0
dependency missing)
Product: Packaging
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: wine-packages
Assignee: wine-bugs(a)winehq.org
Reporter: a34ypool3voiz(a)t-online.de
CC: michael(a)fds-team.de, sebastian(a)fds-team.de
Distribution: ---
Created attachment 64049
--> https://bugs.winehq.org/attachment.cgi?id=64049
log showing missing libfaudio0 deps
I have installed winehq-devel 4.4 on Ubuntu 18.04 amd64.
Currently version 4.5 is available, but installation fails.
Trying the usual "apt-get update && apt-get upgrade && apt-get dist-upgrade"
lists winehq-devel as package that has been kept back.
Then I tried the following:
sudo apt-get install winehq-devel wine-devel wine-devel-amd64 wine-devel-i386
-f
Now two unmet dependencies are listed, which cause the failure: libfaudio0 and
libfaudio0:i386.
Those packages do not exist in the repository.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50251
Bug ID: 50251
Summary: Wrong public key from the repo prevents installation.
Product: Packaging
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: wine-packages
Assignee: wine-bugs(a)winehq.org
Reporter: kristijan.zic(a)gmail.com
CC: dimesio(a)earthlink.net
Distribution: ---
Distro: Ubuntu 20.04
Followed instructions for Focal Fossa here:
https://wiki.winehq.org/Ubuntu
Got this error:
Err:10 https://dl.winehq.org/wine-builds/ubuntu focal InRelease
The following signatures couldn't be verified because the public key is not
available: NO_PUBKEY 76F1A20FF987672F
Reading package lists... Done
W: GPG error: https://dl.winehq.org/wine-builds/ubuntu focal InRelease: The
following signatures couldn't be verified because the public key is not
available: NO_PUBKEY 76F1A20FF987672F
E: The repository 'https://dl.winehq.org/wine-builds/ubuntu focal InRelease' is
not signed.
N: Updating from such a repository can't be done securely, and is therefore
disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration
details.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51920
Bug ID: 51920
Summary: Official package for Arch Linux
Product: Packaging
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: wine-packages
Assignee: wine-bugs(a)winehq.org
Reporter: joseskvolpe(a)gmail.com
CC: dimesio(a)earthlink.net
Distribution: ArchLinux
Wine has packages on the Arch Linux multilib and community repository, they're
currently maintained by Felix Yan (Wine) and Daniel Bermond (Wine-gecko &
Wine-mono)
Problem is... Sometimes there's a huge delay on these packages when they get an
update. This is not a issue only with Wine, it occurs with many other packages
that are maintained in these repositories.
Wine has just released version 6.20, but these repositories are still in
6.16... If we had a official WineHQ repository for Arch Linux distributions
like we got in Ubuntu and Debian, we could get updates for Wine much quicker.
Additionally, having git versions on the official repository would also be neat
to get nightly builds of Wine. ^w^
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51849
Bug ID: 51849
Summary: Debian packaging: When building debian packages,
HARDENING flags will be passed to cross-compiler
Product: Packaging
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-packages
Assignee: wine-bugs(a)winehq.org
Reporter: cybermax(a)dexter.no
CC: dimesio(a)earthlink.net
Distribution: ---
When packages are built on debian, the default "hardening" flags will be passed
to wine/configure. The result from this is that wine/configure tries to do
checks for cross-compiler (mingw-w64) with flags meant to be used for ELF
binaries.
The flags are -Wl,-z,relro
This causes configure to fail several checks for cross-compiler.
The logs from WineHQ official OBS builds here for Debian 11:
https://build.opensuse.org/public/build/Emulators:Wine:Debian/Debian_11/x86…
Failing these checks will cause mingw-w64 to create loads of warnings like:
[ 1042s] In file included from dlls/cabinet/fdi.c:72:
[ 1042s] dlls/cabinet/fdi.c: In function 'FDI_read_string':
[ 1042s] dlls/cabinet/fdi.c:485:9: warning: format '%ld' expects argument of
type 'long int', but argument 6 has type 'INT_PTR' {aka 'long long int'}
[-Wformat=]
[ 1042s] 485 | TRACE("(fdi == %p, hf == %ld, cabsize == %ld)\n", fdi, hf,
cabsize);
[ 1042s] | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~
[ 1042s] | |
[ 1042s] |
INT_PTR {aka long long int}
If you however build without passing -Wl,-z,relro to mingw-w64, configure will
pass a lot more tests, and the compile is quite a lot less noisy:
https://build.opensuse.org/build/home:SveSop/Debian_11/x86_64/wine-devel/_l…
Is there a possibility to avoid passing this flag to the cross-compiler in
wine/configure? From what i gather, the -Wl,-z,relro flag is meant for ELF
binaries, but afaik wine mostly (if not only) uses mingw-w64 to build PE libs,
and thus these flags fail.
You can add export DEB_LDFLAGS_MAINT_STRIP = -Wl,-z,relro to debian/rules, but
that ofc means the ELF binaries built by gcc will not get these hardening
flags.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50891
Bug ID: 50891
Summary: Fedora 33 repository missing wine-*-common x86_64
packages
Product: Packaging
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: wine-packages
Assignee: wine-bugs(a)winehq.org
Reporter: blacknova(a)tut.by
CC: dimesio(a)earthlink.net
Distribution: ---
After recent update of Fedora repository, all x64_64 versions of wine-*-common
packages are missing.
DNF upgrade command complain on broken dependencies:
Problem 1: cannot install the best update candidate for package
wine-staging64-1:6.4-1.1.x86_64
- nothing provides wine-staging-common = 1:6.5-1.2 needed by
wine-staging64-1:6.5-1.2.x86_64
Problem 2: package winehq-staging-1:6.5-1.2.x86_64 requires wine-staging64 =
1:6.5-1.2, but none of the providers can be installed
- cannot install the best update candidate for package
winehq-staging-1:6.4-1.1.x86_64
- nothing provides wine-staging-common = 1:6.5-1.2 needed by
wine-staging64-1:6.5-1.2.x86_64
Problem 3: problem with installed package wine-staging64-1:6.4-1.1.x86_64
- package wine-staging64-1:6.4-1.1.x86_64 requires wine-staging-common =
1:6.4-1.1, but none of the providers can be installed
- cannot install both wine-staging-common-1:6.5-2.1.i686 and
wine-staging-common-1:6.4-1.1.i686
- cannot install the best update candidate for package
wine-staging-common-1:6.4-1.1.i686
- nothing provides wine-staging-common = 1:6.5-1.2 needed by
wine-staging64-1:6.5-1.2.x86_64
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51354
Bug ID: 51354
Summary: WRC 7 needs ID3DUserDefinedAnnotation interface
Product: Wine
Version: 6.11
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
Distribution: ---
Shows WRC 7 window and immediately closes.
0110:trace:d3d11:d3d11_device_context_QueryInterface iface 00000000001E31E8,
iid {b2daad8b-03d4-4dbf-95eb-32ab4b63d0ab}, out 00000000026DA770.
0110:warn:d3d11:d3d11_device_context_QueryInterface
{b2daad8b-03d4-4dbf-95eb-32ab4b63d0ab} not implemented, returning
E_NOINTERFACE.
wine-6.11-158-g542175ab104
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=46615
Bug ID: 46615
Summary: PC Building Simulator doesn't render fonts
Product: Wine
Version: 4.1
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: luca.finizio.mgbx(a)hotmail.it
Distribution: Mint
I tried to play PC Building Simulator v9.3.4 but it's impossible to play the
game because fonts are not rendered. I attached my console output (there are
also errors).
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44950
Bug ID: 44950
Summary: err:ntdll:RtlpWaitForCriticalSection. Supreme
Commander FA
Product: Wine
Version: 3.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: james.ytedmonds(a)gmail.com
Distribution: ---
This bug has affected Supreme Commander: Forged Alliance since pre-2.21. I have
found this bug to affect multiple machines with clean wine prefixes.
At some point during gameplay, the game will either stop entirely or the window
for it will close. The terminal reads:
"
007f:fixme:faultrep:ReportFault 0x153ece4 0x0 stub
0110:err:ntdll:RtlpWaitForCriticalSection section 0xfeec00 "?" wait timed out
in thread 0110, blocked by 007f, retrying (60 sec)
"
The only option after this point is to kill the applications.
I have found several things that seem to make the bug more likely:
*Playing on large maps (definite correlation)
*Using 6+ players (less certain)
*High graphics settings (might affect timing of bug, but AFAIK cannot cause it)
I have tried to override the "ntdll.dll" with one from real windows, but I
believe wine at this time does not support overriding this DLL.
The bug is easy to reproduce, on a large map (i.e. "Betrayal Ocean") it can
occur within 5-10 minutes.
I can get any details and logs needed, but I will need to be told how to get
them (I am not experienced with debugging)
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=48847
Bug ID: 48847
Summary: dotnet471: often gets a critical section timeout
Product: Wine
Version: 5.5
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
Distribution: ---
Created attachment 66764
--> https://bugs.winehq.org/attachment.cgi?id=66764
bt all
I've been seeing this when running winetricks-test, for dotnet46* and
dotnet471. This info is for dotnet471.
austin@laptop ~ $ grep 'wait timed out' /tmp/out.txt | sort -u
0048:err:ntdll:RtlpWaitForCriticalSection section 0x7bd2c220 "loader.c:
loader_section" wait timed out in thread 0048, blocked by 006e, retrying (60
sec)
006e:err:ntdll:RtlpWaitForCriticalSection section 0x110060 "heap.c: main
process heap section" wait timed out in thread 006e, blocked by 0174, retrying
(60 sec)
00ad:err:ntdll:RtlpWaitForCriticalSection section 0x7bd2c220 "loader.c:
loader_section" wait timed out in thread 00ad, blocked by 006e, retrying (60
sec)
00bb:err:ntdll:RtlpWaitForCriticalSection section 0x110060 "heap.c: main
process heap section" wait timed out in thread 00bb, blocked by 0174, retrying
(60 sec)
00e2:err:ntdll:RtlpWaitForCriticalSection section 0x7bd2c220 "loader.c:
loader_section" wait timed out in thread 00e2, blocked by 006e, retrying (60
sec)
0114:err:ntdll:RtlpWaitForCriticalSection section 0x110060 "heap.c: main
process heap section" wait timed out in thread 0114, blocked by 0174, retrying
(60 sec)
0166:err:ntdll:RtlpWaitForCriticalSection section 0x7bd2c220 "loader.c:
loader_section" wait timed out in thread 0166, blocked by 006e, retrying (60
sec)
0169:err:ntdll:RtlpWaitForCriticalSection section 0x7bd2c220 "loader.c:
loader_section" wait timed out in thread 0169, blocked by 006e, retrying (60
sec)
016c:err:ntdll:RtlpWaitForCriticalSection section 0x110060 "heap.c: main
process heap section" wait timed out in thread 016c, blocked by 0174, retrying
(60 sec)
0193:err:ntdll:RtlpWaitForCriticalSection section 0x7bd2c220 "loader.c:
loader_section" wait timed out in thread 0193, blocked by 006e, retrying (60
sec)
winedbg bt all is attached.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50629
Bug ID: 50629
Summary: Old links on https://www.winehq.org/forums
Product: WineHQ.org
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: www-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jkfloris(a)dds.nl
Distribution: ---
Two old links on https://www.winehq.org/forums
1.
"Users might also want to visit the Wine area at Linux Forums"
has a link to http://www.linuxforums.org/forum/wine/linuxforums.org is offline since May 2020
2.
The wine-tests-results(a)winehq.org mailing list isn't used.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=39379
Bug ID: 39379
Summary: test.winehq.org: Show a specific test history for a
machine or platform
Product: WineHQ.org
Version: unspecified
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: www-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
Currently it's possible to see at a glance how specific test fared across Wine
commits and *all platforms*. For instance:
https://test.winehq.org/data/tests/advapi32:service.html
But if a platform has multiple test machines, one where the test has always
failed and another where it has just started failing, one cannot see when the
failures started on the above page.
So it would be nice to have a similar page on a per-platform basis; or one with
all the reports where that test failed regardless of platform.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=48164
Bug ID: 48164
Summary: test.winehq.org should provide an efficient way to
detect new failures
Product: WineHQ.org
Version: unspecified
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: www-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
Problem
-------
test.winehq.org does not allow performing the following tasks efficiently:
1. Detecting when a new failure slips past the TestBot.
One can detect new failures on the per test unit page when specific columns
turn red. But quite often the test unit already has failures so one has to look
at the specific number of failures. Furthermore many test units currently have
failures so this requires checking 80+ pages individually.
2. Detecting when the results on a VM degrade.
After upgrading a machine it's useful to compare it to its previous results.
But the results for each date are on separate pages. So again it's necessary
to check the per-test-unit result pages.
3. Comparing the results of two machines of different platforms.
For instance comparing the results of running Windows 8 to those of
Windows 10 on the same hardware.
Other things that got asked:
4. Sometimes it would be nice to have only the failures, and not all the lines
with skipped tests and todos.
5. In some cases it would also be nice to have pages with only the failures
that happen on TesBot VMs since these are usually easier to reproduce.
Jeremy's page
-------------
Jeremy's test summary page can help with some of that:
https://www.winehq.org/~jwhite/latest.html
But:
* It's not integrated with test.winehq.org which makes it hard to find.
* There are only two states: Success and Failed: So it does not help when a
test goes from having 2 failures to 4, or when it has a set of systematic
failures and a set of intermittent ones.
* The failed / success pattern is not per VM which masks some patterns and does
not help with point 2.
Proposal
--------
A modified version of Jeremy's page could be integrated with test.wnehq.org:
* It would actually be a pair of 'Failures' pages, one for TestBot VMs and one
for all test results. Both would be linked to from the top of the main index
page, for instance using the same type of 'prev | next' text links used on the
other pages.
* Jeremy's result matrix would be extended from three to four dimensions; test
units, test results, time, and number/type of failures.
* As before the results would be grouped per test unit in alphabetical order.
Only the test units having at least one error, recent or not, would be shown.
This could again be in the form of an array ('full report' pages on
test.winehq.org) or simply test unit titles (TestBot jobDetails page style)
with the information about each test unit inside. Clicking on the test unit
name would link to its 'test runs' page on test.winehq.org.
* For each test unit there would be one line per test result having errors. The
first part of the line would have one character per commit for the whole
history available on test.winehq.org. That character would indicate if the test
failed and more.
The second part of the line would be the test result platform and tag. They
would be sorted per platform and alphabetically.
* Each test result would get a one character code:
. Success
F Failure
C Crash
T Timeout
m Missing dll (foo=missing or other error code)
e Other dll error (foo=load error 1359 and equivalent)
_ No test (the test did not exist)
' ' No result (the machine did not run the tests that day)
* These codes would be shown using a monospace font so they would form a
pattern across time and test results:
.....F..F...F..F.mmm Win8 vm1
.....FFFFeFFFFFFeFFF Win8 vm1-ja
...TTCC Win8 vm2-new
......eF...F...F..F. Win10 vm3
* Each character would have a tooltip containing details like the meaning of
the letter, the number of failures, or the dll error message.
They would also link to the corresponding section of the test report.
* In addition to the character the background would be color coded to make
patterns more visible.
. Green
F Green to yellow to red gradient
C Dark red
T Purple/pink
m Cyan
e Dark blue
_ Light gray
' ' White
* The green-yellow-red gradient would be what allows detecting changes in the
number of test failures. That gradient must be consistent for all lines of a
given test unit's pattern.
Furthermore the gradient must not be computed based on the test result's
number of failures. That is, if a test unit has either 100 or 101 failures,
those must not have nearly indistinguishable colors. Instead the set of all
different failure counts for the test unit should be collected. Zero should be
added to that set. Then these values should be sorted and a color attributed
for each *index*. Then the background color is selected based on the index of
that result's failures count.
It is expected that each set will be relatively small so that the colors will
be reasonably far apart, making it easy to distinguish a shift from 4 to 6
failures even if there are 100 failures from time to time.
Also note hat adding zero to the set essentially reserves green for
successful results.
Implementation feasibility
--------------------------
* No changes in dissect.
* In gather, generate a new testunits.txt file containing one line per test
unit:
- The data source would be the per-report summary.txt files.
-> These don't indicate when a timeout has occurred so timeouts will appear
as F instead which is acceptable for a first implementation.
- The first line would contain a star followed by the tags of all the test
runs used to build the file:
- The other lines would contain the name of the test unit followed by
space-separated pairs of result code/failure count and result tag (including
the platform).
- A line would be put out even if the test unit had no failure.
For instance, the commit1 testunit.txt file could contain:
* win8_vm1 win8_vm1-ja win8_vm2-new win10_vm3
foo:bar 43 win8_vm1-ja C win8_vm2-new e win10_vm3
foo:bar2
- In the example above win8_vm1 only appears on the first line. This means
WineTest was run on that machine but had no failure at all.
- If the results for commit2 refer to a win8_vm4 machine, we will know that
the reason win8_vm4 does not appear in commit1 file is not because all the
tests succeeded, but because WineTest was not run on win8_vm4 for commit1. This
means that the result code for win8_vm4 for commit1 should be ' '. not '.' for
all test units.
- If commit2 has results for the foo:bar3 test unit, then we will know the
reason it is not present in the commit1 file is not because all the test runs
were successful, but because foo:bar3 did not exist yet. So its result code
would be '_', not '.'.
* Add a new build-failures script to generate both failures pages.
- This script will need to read the testunits.txt file for all the commits.
The simplest implementation will be to read all the data into memory before
generating the page. This will avoid having to deal with keeping the current
test unit synchronized between all of the testunits.txt files when a new test
unit has been added.
- The combined size of the testunits.txt files is expected to be reasonable,
within a factor of 3 of the summary.txt files. For reference, here is some data
about the sizes involved:
$ du -sh data
21G data
$ ls data/*/*/report | wc -l
2299
$ cat data/*/*/report | wc
34,087,987 231,694,407 2,104,860,095
$ cat data/*/*/report | egrep '(: Test failed:|: Test succeeded inside todo
block:|done [(]258)|Unhandled exception:)' | wc
567,158 6,275,504 53,202,999
$ cat data/*/summary.txt | wc
186,219 3,046,363 30,596,901
- Having a function to generate the page will allow calling it twice in a row
to generate both pages without having to load and parse the testunits.txt files
twice.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51352
Bug ID: 51352
Summary: test.winehq.org should distinguish "too much data"
errors from others
Product: WineHQ.org
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: www-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
The new patterns page treats the "test printed too much data" failures like any
other. It would be better to use another symbol and color when there is no
other failure.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52088
Bug ID: 52088
Summary: Update favicon to 32X32
Product: WineHQ.org
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: trivial
Priority: P2
Component: www-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: 2ndforwine(a)inmano.com
Distribution: ---
The 16x16 looks very blurry when compared to other web-sites.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50630
Bug ID: 50630
Summary: Old link on https://www.winehq.org/news
Product: WineHQ.org
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: www-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jkfloris(a)dds.nl
Distribution: ---
At the bottom of the page there is a link to
World Wine News Archive - https://www.winehq.org/wwn
The last "news" item is from 2017.
Maybe it is an idea to remove this link.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50516
Bug ID: 50516
Summary: Broken link
'https://wiki.winehq.org/Useful_Registry_Keys'
Product: WineHQ.org
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: www-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jose.relland(a)free.fr
Distribution: ---
Hi, thank you for your time.
I noted that the linnk:
"Wine Man Page" (at the bottom of the page) is broken.
Send to 404 page error.
Best 2021 year :)
José from France
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50512
Bug ID: 50512
Summary: Wiki /Bugs links broken, can't edit them
Product: WineHQ.org
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: www-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ddascalescu+wine(a)gmail.com
Distribution: ---
I've created an account to edit the wiki. May I please have permission to do
so? I'm User:Dandv on Wikipedia as well.
Due to the extensive reorg of https://wiki.winehq.org/Wine_User's_Guide, the
links at https://wiki.winehq.org/Bugs in "You installed and ran the application
using Wine, not on your Windows installation" are broken.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=42309
Bug ID: 42309
Summary: The Crew (Uplay) crashes at start
Product: Wine
Version: 2.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: o.dierick(a)piezo-forte.be
Distribution: ---
Created attachment 57043
--> https://bugs.winehq.org/attachment.cgi?id=57043
Unhandled page fault read access to 0x0 in 64-bit code backtrace
After the loading screen has closed, the screen goes black and then wine
crashes with a read access to 0x00000000 in 64-bit code.
The terminal is also filled with DirectX 11 fixme's.
Tested on wine 2.0 + staged patch from bug 41356.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51437
Bug ID: 51437
Summary: If Windows version changes from 7 to 10, Microsoft
Edge calls unimplemented function
uiautomationcore.dll.UiaRaiseAutomationPropertyChanged
Event
Product: Wine
Version: 6.12
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: uiautomationcore
Assignee: wine-bugs(a)winehq.org
Reporter: alexhenrie24(a)gmail.com
Distribution: ---
Steps to reproduce:
1. Install Wine Staging (Edge will not start on vanilla Wine).
2. Run `wine MicrosoftEdgeSetup.exe` (make sure to download the installer for
Windows 7).
3. Run `winecfg` and change the Windows version from 7 to 10.
4. Run `wine msedge`.
If the Windows version is set to 10 from the beginning (and Edge's Windows 10
installer is used), the crash does not occur. However, it's a reasonable use
case to install Edge with default Wine settings and then "upgrade" Wine to
Windows 10 later.
$ sha256sum MicrosoftEdgeSetup.exe
c449a35ff96012ae26336ff630ced945d85f83b162b041606549c555b8a997c8
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50158
Bug ID: 50158
Summary: Oculus Runtime won't start: "Could not load file or
assembly 'Daybreak'"
Product: Wine
Version: 5.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: criteria32(a)gmail.com
Distribution: ---
Created attachment 68674
--> https://bugs.winehq.org/attachment.cgi?id=68674
Crash log
Can be downloaded at oculus.com/setup or with this direct link:
https://www.oculus.com/download_app/?id=1582076955407037
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45103
Bug ID: 45103
Summary: FlixGrab: Crashes on launch after showing the splash
screen
Product: Wine
Version: 3.7
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: lucas.halbig(a)gmail.com
Distribution: ---
Created attachment 61276
--> https://bugs.winehq.org/attachment.cgi?id=61276
backtrace file when app crashed
When attempting to launch
https://www.freegrabapp.com/flixgrab
after installation it failes to go past the splash screen.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50460
Bug ID: 50460
Summary: Regression on installing mdac28 on 6.0-rc5 was ok in
5.0.4
Product: Wine
Version: 6.0-rc5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: pierre(a)couderc.eu
Distribution: ---
Created attachment 69085
--> https://bugs.winehq.org/attachment.cgi?id=69085
log of the trial
Using :
sudo rm -rI .wine/
WINEARCH=win32 winecfg
winetricks mdac28
wine .wine/drive_c/windows/system32/odbcad32.exe
fails on last version (from winehq-devel from deb
https://dl.winehq.org/wine-builds/debian/ bullseye main debian) and is ok with
default bullseye release (5.0.4).
odbcad32.exe box is not displayed.
Full (small...) listing in attachment
I am not able to know if the problem is wine or winetricks. But I am surprised
that msado15 is installed as ado is not needed for mdac adn odbs...
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51901
Bug ID: 51901
Summary: Warcraft 3 disconnects Randomly when using bonjour
service and w3champions
Product: Wine
Version: 6.19
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: kostile(a)gmail.com
Distribution: ---
I didn't get a full trace log, but below is the output I get when the game
disconnects randomly:
npacked/flo-worker.exe:
/home/ubuntu/buildbot/runners/wine/wine-src/dlls/ntdll/unix/thread.c:1773:
ntdll_set_exception_jmp_buf: Assertion `!jmp ||
!ntdll_get_thread_data()->jmp_buf' failed.
0630:err:virtual:virtual_setup_exception nested exception on signal stack in
thread 0630 addr 0x7fd6118a5d22 stack 0x67fbddb0
There doesn't seem to be any reason, it just randomly disconnects. Could be 2
minutes into a game or 30 minutes into a game.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=48758
Bug ID: 48758
Summary: ConEmu Ctrl+c has different behavior
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: rpisl(a)seznam.cz
Distribution: ---
In ConEmu, Ctrl+c behavior is different on Wine and Windows.
ConEmu+Cmd on Windows:
Ctrl+c breaks current command and starts new empty prompt
Ctrl+C shows ^C
ConEmu+Cmd on Wine:
Ctrl+c shows 'c'
Ctrl+C terminates ConEmu completely
ConEmu+Far Manager+console application on Windows:
Ctrl+c terminates the application
Ctrl+C shows ^C
ConEmu+Far Manager+console application on Wine:
Ctrl+c does nothing or shows 'c'
Ctrl+C terminates the application
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=21936
Summary: rtld mmap failed mapping on OpenBSD
Product: Wine
Version: 1.1.40
Platform: x86
URL: http://www.openbsd.org/cgi-bin/cvsweb/ports/emulators/
wine/patches/patch-libs_wine_mmap.c?rev=1.1;content-ty
pe=text%2Fplain
OS/Version: OpenBSD
Status: NEW
Keywords: download, patch, source
Severity: blocker
Priority: P2
Component: loader
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: austinenglish(a)gmail.com
/home/austin/wine-git/loader/wine: rtld mmap failed mapping
/home/austin/wine-git/dlls/ntdll/ntdll.dll.so.
wine: failed to initialize: File not found
Patch in url fixes the loader on OpenBSD. Need to test on other OS's before
submitting to wine-patches. Review of the patch in the meantime is appreciated.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=29354
Bug #: 29354
Summary: Microsoft Virtual PC 2007 SP1 installer fails to get
past the "Product Key" dialog
Product: Wine
Version: 1.3.34
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: msi
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: focht(a)gmx.net
Classification: Unclassified
Hello,
split off bug mentioned in http://bugs.winehq.org/show_bug.cgi?id=17512#c3 to
track what is most likely a regression ...
--- quote ---
Tested in 1.3.19
Didn't crash but I couldn't get past the "Product Key" screen. The "Next"
button didn't seem to do anything.
--- quote ---
The problem in Microsoft Virtual PC 2007 SP1 installer is the
"ValidateProductID" standard action.
Dump using ORCA:
--- snip ---
CustomerInformationDialog NextButton NewDialog ReadyToInstallDialog
PIDRET = 0 4
CustomerInformationDialog NextButton DoAction CA_ValidatePID NOT
ProductID AND PIDKEY AND PIDKEY<>" " 1
CustomerInformationDialog NextButton DoAction CA_InstallForAllUsers
NOT VPC2004INSTALLED 2
CustomerInformationDialog NextButton DoAction
CA_SetTargetPathOnUpgrade VPC2004INSTALLED 3
--- snip ---
First condition, if true -> CA_ValidatePID gets executed.
--- snip ---
0023:trace:msi:MSI_EvaluateConditionW L"NOT ProductID AND PIDKEY AND PIDKEY<>\"
\""
...
0023:trace:msi:msi_get_property returning L"PWCVDGDPM7P23VYG6QM4R8Y8T" for
property L"ProductID"
...
0023:trace:msi:msi_get_property returning L"PWCVDGDPM7P23VYG6QM4R8Y8T" for
property L"PIDKEY"
...
0023:trace:msi:MSI_EvaluateConditionW 0 <- L"NOT ProductID AND PIDKEY AND
PIDKEY<>\" \""
--- snip ---
(not fulfilled)
Another condition to reach "ReadyToInstallDialog" is "PIDRET = 0".
--- snip ---
0023:trace:msi:MSI_ProcessMessage (nil) (nil) (nil) 0 10 L"Action start
18:26:06: ValidateProductID."
0023:trace:msi:msi_get_property returning
L"74216<````=````=````=````=`````>@@@@@" for property L"PIDTemplate"
0023:fixme:msi:ACTION_ValidateProductID partial stub: template
L"74216<````=````=````=````=`````>@@@@@" key L"PWCVDGDPM7P23VYG6QM4R8Y8T"
0023:trace:msi:msi_set_property 0x13ce60 L"ProductID"
L"PWCVDGDPM7P23VYG6QM4R8Y8T"
0023:trace:msi:MSI_ProcessMessage (nil) (nil) (nil) 0 10 L"Action ended
18:26:06: ValidateProductID. Return value 0."
...
0023:trace:msi:MSI_EvaluateConditionW L"PIDRET = 0"
0023:trace:msi:msi_get_property property L"PIDRET" not found
0023:trace:msi:MSI_EvaluateConditionW 0 <- L"PIDRET = 0"
--- snip ---
The "PIDRET" property never exists hence the installation is stuck in
"CustomerInformationDialog".
If you google for "Adding PIDRET property" you will find many similar looking
msi logs, suggesting that this property is added during ValidatePID custom
action:
--- snip ---
MSI (c) (DC:20) [17:55:05:750]: Doing action: ValidatePID
MSI (c) (DC:20) [17:55:05:750]: Note: 1: 2205 2: 3: ActionText
Action 17:55:05: ValidatePID.
Action start 17:55:05: ValidatePID.
...
MSI (c) (DC!3C) [17:55:05:875]: PROPERTY CHANGE: Adding PID property. Its value
is '58730-000-0000007-05734'.
MSI (c) (DC!3C) [17:55:05:875]: PROPERTY CHANGE: Adding ProductID property. Its
value is '58730-000-0000007-05734'.
...
MSI (c) (DC!3C) [17:55:05:875]: PROPERTY CHANGE: Adding PIDRET property. Its
value is '0'.
Action ended 17:55:05: ValidatePID. Return value 1.
--- snip ---
Because ProductID was set earlier during ValidateProductID standard action,
CA_ValidatePID is never executed.
http://source.winehq.org/git/wine.git/blob/8cc5561fbf9f3250fbd2d986390e4013…
If you remove line 6891 the installer executes the custom action which allows
to proceed and let the installation finally succeed.
You need 'winetricks mfc42' for CA_ValidatePID.
Regards
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=51923
Bug ID: 51923
Summary: api-ms-win-core-windowserrorreporting-l1-1-1.dll not
found
Product: Wine
Version: 6.16
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: api-ms-win-*
Assignee: wine-bugs(a)winehq.org
Reporter: henriquesilvapedroso74(a)hotmail.com
Distribution: ---
Windows 10 App fails to launch due to the DLL
"api-ms-win-core-windowserrorreporting-l1-1-1.dll" not being found, one reddit
user (DarkShadow4444) said to me that it is a virtual dll from Windows apiset.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=16221
Summary: Nota Bene requires AUTOEXEC.NT
Product: Wine
Version: 1.1.9
Platform: PC
URL: https://www.notabene.com/download/demos/nbdemo80.exe
OS/Version: Linux
Status: NEW
Keywords: download, Installer
Severity: minor
Priority: P2
Component: dos
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: austinenglish(a)gmail.com
Nota Bene, on install, checks for AUTOEXEC.NT in system32. If it doesn't find
it, it restores its own copy, but we should have our own copy. Shouldn't take
much to implement.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=46648
Bug ID: 46648
Summary: Core Temp Error
Product: Wine
Version: 4.1
Hardware: x86-64
URL: https://www.alcpu.com/CoreTemp/
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: luca.finizio.mgbx(a)hotmail.it
Distribution: Mint
Created attachment 63570
--> https://bugs.winehq.org/attachment.cgi?id=63570
console output
I downloaded and installed Core Temp from https://www.alcpu.com/CoreTemp/ but I
get an Error window when trying to launch it. The error window says "Core Temp
did not find any supported processors. This program will not continue."
I attach my console output.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=16222
Summary: Nota Bene requires CONFIG.NT
Product: Wine
Version: 1.1.9
Platform: PC
URL: https://www.notabene.com/download/demos/nbdemo80.exe
OS/Version: Linux
Status: NEW
Keywords: download, Installer
Severity: minor
Priority: P2
Component: dos
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: austinenglish(a)gmail.com
Nota Bene, on install, checks for CONFIG.NT in system32. If it doesn't find it,
it restores its own copy, but we should have our own copy. Shouldn't take much
to implement.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=34259
Bug #: 34259
Summary: cygwin 2.819 installer hangs during postinstall
Product: Wine
Version: 1.7.0
Platform: x86
OS/Version: Linux
Status: NEW
Keywords: download, Installer, source
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: austinenglish(a)gmail.com
Classification: Unclassified
Created attachment 45597
--> http://bugs.winehq.org/attachment.cgi?id=45597
terminal output
Similar to bug 24018, but that should be fixed in cygwin's upstream.
Install progresses as normal, when the postinstall script process start, it
hangs.
austin@aw25 ~ $ sha1sum setup-x86.exe
1574ef1833e07af1d6b33b80229d15c1b46c4319 setup-x86.exe
austin@aw25 ~ $ du -h setup-x86.exe
712K setup-x86.exe
austin@aw25 ~ $ wine --version
wine-1.7.0
May be related to bug 30397.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=33188
Bug #: 33188
Summary: wine explorer: wrong behavior when dragging with no
items selected
Product: Wine
Version: 1.5.25
Platform: x86
OS/Version: Linux
Status: NEW
Keywords: download, source
Severity: minor
Priority: P2
Component: comctl32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: austinenglish(a)gmail.com
Classification: Unclassified
Apologies if this is already reported, apparently it's been around since at
least 1.2, but I couldn't find a report for it.
Noticed in notepad++, but wine explorer has the same behavior.
$ wine explorer
click in the bottom right where no files are (you may need a folder with a few
files, but not a ton..)
drag
the top item in list is selected, even though the mouse is nowhere nearby
this does not occur on windows with notepad++
native comctl32 works around it.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.