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=52349
Bug ID: 52349
Summary: Vortex Mod Manager Starts but Infinitely Loads
Product: Wine
Version: 7.0-rc4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: nekoNexus(a)protonmail.ch
Distribution: ---
SHA256 of installer executable:
ee6a45b1a4f88e1c5905b3dc9b25578a520279ff8d8be14b1f56b041388fcd6a
Download location:
https://github.com/Nexus-Mods/Vortex/releases/download/v1.4.16/vortex-setup…
SHA256 of log .tar.gz file:
f87b5914373ab521ebcb0ea0ffe0679e3968c7c6a1f8fef10f64496fcdc6835f
WARNING:
- The compressed tarball is about 149.9 MiB
- It contains a 6 GB log file (it was difficult to not get it to expand so
quickly and to log it in the first place)
- I recommend anyone only attempt to go through it if they have a lot of RAM,
seriously.
- Since it greatly exceeds the attachment limit, I had to upload it to a cloud
hosting site (namely, mega.nz)
Log download link:
https://mega.nz/file/ZiJAkB5Y#UgnbfHO99ldqN1cbAs0KAxXxxNVNPoKKdAM27RsXmEM
-----
I created a (non-staging) Wine prefix and used winetricks afterwards like so:
winetricks -q dotnet48 vcrun2017 python27
None of these are required to install the program, but the the program does use
.NET at runtime and MSVC2017 and python27+ are build requirements, so I added
them anyway just to be sure.
After the winetricks and program installation, the program automatically
launches itself but hangs on "Loading extensions" for literally forever -
generating that gigantic log file and it does so somewhat quickly, and my only
means I had of logging it was with &> because my attempts to do so within the
terminal myself just crashes my terminal.
However, Kate (the KDE text editor) CAN read the entirety of the file but it
takes a bit to actually load it initially. As someone unfamiliar with any of
the contents though, there's not much I can say about it aside from that it's
baffling why it would be so large.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=52220
Bug ID: 52220
Summary: TMIDI Player, Cherry: Playback with multiple MIDI
ports is broken
Product: Wine
Version: 7.0-rc1
Hardware: x86-64
URL: https://www.vector.co.jp/soft/dl/win95/art/se038910.ht
ml
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winealsa.drv
Assignee: wine-bugs(a)winehq.org
Reporter: kakurasan(a)gmail.com
Regression SHA1: 3d57cc2863f2f9a5ace40d29317b3ff4357fd119
Distribution: ---
Created attachment 71297
--> https://bugs.winehq.org/attachment.cgi?id=71297
Sample MIDI file that uses 2 MIDI ports
When the apps are configured to use multiple MIDI ports, playback is broken if
the song (MIDI file) uses multiple MIDI ports.
Downloads:
* TMIDI Player: https://www.vector.co.jp/soft/dl/win95/art/se038910.html
* Cherry: https://www.vector.co.jp/soft/dl/win95/art/se071842.html
Steps to reproduce:
1. Install ja_JP.UTF-8 locale
2. Execute "winetricks fakejapanese_ipamona" for Japanese fonts
3. Download TMIDI Player
4. Install/run TMIDI Player on ja_JP.UTF-8 locale
5. Open menu item "オプション(O) - MIDIè¨å®š(M)" (or press Alt-o and Enter) and set
MIDI Port A and B to valid and different MIDI ports
6. Open/play the attached MIDI file
This is a regression introduced by:
commit 3d57cc2863f2f9a5ace40d29317b3ff4357fd119
Author: Jacek Konieczny <jajcus(a)jajcus.net>
Date: Wed Feb 12 12:53:54 2020 -0600
winealsa.drv: Send MIDI events to port subscribers.
This way changes to the port connections made by other applications will be
honoured.
Signed-off-by: Jacek Konieczny <jajcus(a)jajcus.net>
Signed-off-by: Andrew Eikum <aeikum(a)codeweavers.com>
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
--
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=52173
Bug ID: 52173
Summary: kodi crashes at start: Call to unimplemented function
wsdapi.dll.WSDCreateDiscoveryProvider, aborting
Product: Wine
Version: 6.22
Hardware: x86-64
URL: https://mirrors.kodi.tv/releases/windows/win64/kodi-19
.3-Matrix-x64.exe
OS: Linux
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: xerox.xerox2000x(a)gmail.com
Distribution: ---
Created attachment 71223
--> https://bugs.winehq.org/attachment.cgi?id=71223
patch with stub stub
As the title says. Attached stub implementation gets it around this crash.
Will send later to list
Note: Starts further fine if I do 'winetricks dxvk141' but maybe my graphics
card is too "simple', and this is not needed for other cards?
--
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=52799
Bug ID: 52799
Summary: Can't add repository
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: slayersnet2012(a)gmail.com
CC: dimesio(a)earthlink.net
Distribution: ---
Add Repository gives an error Message like this:
Fehl:7 https://dl.winehq.org/wine-builds/ubuntu jammy/main i386 Packages
Datei hat eine unerwartete Größe (4812 != 6744). Eventuell läuft gerade eine
Spiegel-Synchronisierung? [IP: 151.101.114.217 443]
Hashes of expected file:
- Filesize:6744 [weak]
-
SHA512:a15c76a48f721f44fadd27eacd67513d98524685955d8cf59da3ab4d43a2916969169bb53f0e76582e6cd41e55a6294426a364bf62c4365b79669ae94bf9a515
- SHA256:6e3c6241b7a543f121a60c8e91642652113eea4e7ab898709d0e6e5a9211e765
- SHA1:f9853bd8bd6cd2361f6458911fdbcd9ba666f683 [weak]
- MD5Sum:34607ca91b2aecc163babf031878cfa5 [weak]
Release file created at: Sat, 09 Apr 2022 15:20:32 +0000
--
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=52697
Bug ID: 52697
Summary: missing fonts in unity games
Product: Wine
Version: 7.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdi32
Assignee: wine-bugs(a)winehq.org
Reporter: galtgendo(a)o2.pl
Distribution: ---
Before you ask, I've already seen some of those "install Arial/Arial Bold"
'solutions.
But it's actually a bit more complicated.
As a fallback font for not embedded font resources Unity is looking up Arial...
Only it actually isn't.
It starts with Arial name and any extra values like weight (which I suspect
leads to Arial Bold - though just guessing that part), but actually assumes
full font substitution is working behind the font.
I assert that, cause I've run into a Japanese game that requested Arial, but
expected it to have cjk glyphs. While Arial Unicode kind of worked, I'm pretty
sure it was not what was originally requested. Also, Arial Unicode is
suboptimal on quite a few levels.
Though it might be that to start the process, a font file with font name
containing 'Arial' needs to be present in drive_c/windows/fonts. One way or
another, standard method of
HKEY_CURRENT_USER\Software\Wow6432Node\Wine\Fonts\Replacements fails.
--
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=52732
Bug ID: 52732
Summary: Garbage user-name crated with wine, not the proper
user-name like in older versions.
Product: Wine
Version: 7.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: rencer(a)euromail.hu
Distribution: ---
I'm not sure exactly when (the latest 7.4 version or which previous version)
this started to happen, because for a very long time I used Lutris to manage
Wine-versions and my Windows programs. Because of Lutris,I don't even have Wine
installed system-wide.
Sadly with the newest system (Manjaro XFCE) update someting in Python is
totally broken, and because of that Lutris won't work anymore, so I had to
install wine from system repo.
The latest version in 7.4
The problem is when I createa a new (or try to change an existing wineprefix to
use this system version), the user name is not my real username that I logged
in with. Now wine creates a strange garbage user name: "u@". Previously it was
correct and alway created the proper user folder, with the user who logged in
and run wine.
Long time ago, before I started using Lutris (I'm not sure which wine version
that was, around 4.x) I used command line to run wine, create prefixes, or run
any Windows programs and never was this bug. Also most of the progrmas I
installed with older versions and later never changed it, I think the last
version that I used with Lutris is 6.something and it also don't had this
user-name bug.
Problem is that all programs in any existing Wine-prefixes that was created
with Lutris, (with the PROPER user-name) are broken, settings are lost, saves
won't find, etc.,etc.,etc. because all the settings/saves are located in the
correct user-name folder and not in this new bugged garbage "@u" name. First I
thouth I lost all my files, and when I checked them with file-manager, that is
how I realised this strange behaviour.
Copying the files to the new garbage name location in NOT working all the time,
because many times programs store their settings, saved files, etc. in the
registry-database, so, this bug really broke many things.
--
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=52598
Bug ID: 52598
Summary: Update instructions for repository key usage due to
deprecation of apt-key
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: shtetldik(a)gmail.com
CC: dimesio(a)earthlink.net
Distribution: ---
When using the repo, apt update produces such warning:
W: https://dl.winehq.org/wine-builds/debian/dists/testing/InRelease: Key is
stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the
DEPRECATION section in apt-key(8) for details.
>From man apt-key
DEPRECATION
Except for using apt-key del in maintainer scripts, the use of apt-key
is deprecated. This section shows how to replace existing use of apt-key.
If your existing use of apt-key add looks like this:
wget -qO- https://myrepo.example/myrepo.asc | sudo apt-key add -
Then you can directly replace this with (though note the recommendation
below):
wget -qO- https://myrepo.example/myrepo.asc | sudo tee
/etc/apt/trusted.gpg.d/myrepo.asc
Make sure to use the "asc" extension for ASCII armored keys and the
"gpg" extension for the binary OpenPGP format (also known as "GPG key public
ring"). The binary OpenPGP format works for all apt versions, while the ASCII
armored format
works for apt version >= 1.4.
--
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=6682
temp82(a)luukku.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |temp82(a)luukku.com
--- Comment #75 from temp82(a)luukku.com ---
(In reply to Artem S. Tashkinov from comment #74)
> Can't reproduce in Wine 7.6, marking fixed.
works here as well linuxmint Mate. wine 7.6.
--
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=6682
Artem S. Tashkinov <aros(a)gmx.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
URL|http://www.techspot.com/dow |https://web.archive.org/web
|nloads/299-irfanview.html#d |/20170711052934/https://www
|ownload_scroll |.irfanview.info/files/iview
| |444.zip
Resolution|--- |FIXED
--- Comment #74 from Artem S. Tashkinov <aros(a)gmx.com> ---
Can't reproduce in Wine 7.6, marking fixed.
--
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=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=52728
Bug ID: 52728
Summary: wine-7.5 build fails in Ubuntu 18.04
Product: Wine
Version: 7.5
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: winealsa.drv
Assignee: wine-bugs(a)winehq.org
Reporter: dimesio(a)earthlink.net
Distribution: ---
Created attachment 72087
--> https://bugs.winehq.org/attachment.cgi?id=72087
Ubuntu 18.04 failed build log
All the other builds were fine, but it failed in winealsa.drv in Ubuntu 18.04
[ 2042s] dlls/winealsa.drv/alsamidi.c:117:8: error: unknown type name
'uint64_t'
[ 2042s] static uint64_t get_time_msec(void)
[ 2042s] ^~~~~~~~
[ 2042s] dlls/winealsa.drv/alsamidi.c: In function 'get_time_msec':
[ 2042s] dlls/winealsa.drv/alsamidi.c:123:17: error: 'uint64_t' undeclared
(first use in this function); did you mean 'u_int64_t'?
[ 2042s] return (uint64_t)now.tv_sec * 1000 + now.tv_nsec / 1000000;
[ 2042s] ^~~~~~~~
[ 2042s] u_int64_t
[ 2042s] dlls/winealsa.drv/alsamidi.c:123:17: note: each undeclared identifier
is reported only once for each function it appears in
[ 2042s] dlls/winealsa.drv/alsamidi.c:123:26: error: expected ';' before 'now'
[ 2042s] return (uint64_t)now.tv_sec * 1000 + now.tv_nsec / 1000000;
[ 2042s] ^~~
[ 2042s] dlls/winealsa.drv/alsamidi.c:126:22: error: expected ';' before 'now'
[ 2042s] return (uint64_t)now.tv_sec * 1000 + now.tv_nsec / 1000000;
[ 2042s] ^~~
[ 2042s] dlls/winealsa.drv/alsamidi.c:127:1: warning: control reaches end of
non-void function [-Wreturn-type]
[ 2042s] }
[ 2042s] ^
[ 2042s] Makefile:130009: recipe for target 'dlls/winealsa.drv/alsamidi.o'
failed
[ 2042s] make[1]: *** [dlls/winealsa.drv/alsamidi.o] Error 1
--
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=52698
Bug ID: 52698
Summary: JW Scheduler installer fails to start: "Requires
Microsoft .NET Framework 4.5.2"
Product: Wine
Version: 7.4
Hardware: x86-64
URL: https://jwscheduler.com/jw-christian-life-ministry-mee
ting-scheduler/
OS: Linux
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: mscoree
Assignee: wine-bugs(a)winehq.org
Reporter: xerox.xerox2000x(a)gmail.com
Distribution: ---
It checks for the reg key DWORD
HKEY_LOCAL_MACHINE\Software\Microsoft\NET Framework Setup\NDP\v4\Full\Servicing
which is not present.
After manually creating it, the app installs and starts for me
I guess this should be fixed in Mono (?)
--
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=52658
Bug ID: 52658
Summary: Swisslog
Product: Wine
Version: 7.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: kvradio(a)seznam.cz
Distribution: ---
EndeavourOS Wine 7.4-1 Swisslog http://www.swisslogforwindows.com/download.html
has stopped working and freezes logo on startup.. No error displayed.
Version 7.3 and earlier works very well
(If I try to replace the folder /usr/lib32/wine from 7.3 package works 7.4
again)
--
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=52660
Bug ID: 52660
Summary: chunk allocator for GL uniform buffers kills
performance in World of Warships
Product: Wine
Version: 7.4
Hardware: x86-64
URL: https://worldofwarships.eu/
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: janbraun(a)gmx.net
Regression SHA1: 86f0ae8efb17ce688986971d24c3e25840a2beef
Distribution: ---
I've found and bisected a huge performance regresssion in World Of Warships:
With 86f0ae8efb17ce688986971d24c3e25840a2beef "wined3d: Use the chunk allocator
for GL uniform buffers." applied, my framerate is around 18-20fps during
gameplay. With that patch reverted, it's back at >=60fps. The code moved around
in the meantime, but simply commenting out the "case GL_UNIFORM_BUFFER:" in
use_buffer_chunk_suballocation() restores performance on wine 7.4 (= current
git HEAD) as well.
I have the subjective impression that other games might be affected too (things
feel a bit more sluggy), but certainly nowhere as severely as WoWS. I didn't
further test/benchmark, however, because WoWS was such a nice reproducer.
Running mesa-21.3.7 on amdgpu. Please holler if you need more info.
--
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=52638
Bug ID: 52638
Summary: The 64-bit winmm:mci fails and crashes in
test_openCloseWAVE() in Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: winmm&mci
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
The 64-bit winmm:mci crashes in test_openCloseWAVE() in Wine:
mci.c:389: Test failed: mci sysinfo all quantity returned
MCIERR_UNRECOGNIZED_COMMAND
mci.c:398: Test failed: sysinfo all quantity string and command differ
Unhandled exception: page fault on read access to 0x000000000000020d in 64-bit
code (0x00000000709b9ca1).
[...]
Backtrace:
=>0 0x00000000709b9ca1 _wcsicmp_l+0x91(str1=*** Invalid address
0x0000000000000002 ***
Internal symbol error: unable to access memory location 0000000000000002,
str2=*** Invalid address 0x0000000000000000 ***
Internal symbol error: unable to access memory location 0000000000000000,
locale=000000000064E980) [Z:\home\winetest\winetest\src\dlls\msvcrt\wcs.c:132]
in ucrtbase (0x000000000004dd50)
1 0x00000000709b9d6c _wcsicmp+0xc(str1=<internal error>, str2=<internal
error>) [Z:\home\winetest\winetest\src\dlls\msvcrt\wcs.c:158] in ucrtbase
(0x00000000709b9d60)
2 0x0000000000bf8057 MCI_FindCommand+0x38(s2=<internal error>, s1=<internal
error>) [Z:\home\winetest\winetest\src\dlls\winmm\mci.c:946] in winmm
(0x00000000709b9d60)
3 0x0000000000bf8057 MCI_FindCommand+0x67(uTbl=<internal error>,
verb=<register RDI not accessible in this frame>)
[Z:\home\winetest\winetest\src\dlls\winmm\mci.c:938] in winmm
(0x00000000709b9d60)
4 0x0000000000bfbcc7 mciSendStringW+0xc57(lpstrCommand=<internal error>,
lpstrRet=[<register RSP not accessible in this frame>, uRetLen=[<register RSP
not accessible in this frame>, hwndCallback=[<register RSP not accessible in
this frame>) [Z:\home\winetest\winetest\src\dlls\winmm\mci.c:1460] in winmm
(0x00000000003e0000)
https://test.winehq.org/data/patterns.html#winmm:mci
This only happens with the 64-bit build but as far as I can tell it is
systematic and impacts all machines.
A bisect pointed to the following commit as the trigger:
commit 7c76aa05a9d27dd6f5705c4ef90c16862af14f3e
Author: Jacek Caban <jacek(a)codeweavers.com>
Date: Mon Mar 7 14:42:32 2022 +0100
win32u: Move class management implementation from user32.
Signed-off-by: Jacek Caban <jacek(a)codeweavers.com>
Signed-off-by: Huw Davies <huw(a)codeweavers.com>
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
--
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=52340
Bug ID: 52340
Summary: wine-mono + RMS Express: COM Port errors connecting to
radios
Product: Wine
Version: 7.0-rc4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: mscoree
Assignee: wine-bugs(a)winehq.org
Reporter: eric.wheez(a)gmail.com
Distribution: ---
Hello again,
I just wanted to report in a "not implemented" exception in wine-mono. I
believe that "System.IO.Ports.SerialPort.set_ReceivedBytesThreshold" not
implemented in wine-mono is causing RMS Express to not be able to control the
radio (channel selection and "push-to-talk"/"PTT" switch) over USB connection.
Normal behavior is for RMS Express to tell the radio what radio channel to
send/receive on & when to transmit/listen (via PTT switch). This behavior is
working on RMS Express via Windows. This behavior is also working with RMS
Express on Debian 10 VM with wine & .NET 4.6 (I had to set `sudo adduser $USER
dialout && sudo reboot` to set permissions for the COM port for the user
account so before channels/PTT worked .NET 4.6 though).
The not implemented exception pops up in the linux terminal with wine-mono
exactly at the same time that the (known-working-with-.NET4.6) COM port is said
to be inaccessible. I've included the short log of the wine-mono not
implemented exception at the of this post.
[Setup]
OS: Debian 10 (VMware Workstation on a Windows laptop)
Wine: wine-7.0-rc4 devel
Wine Mono: wine-mono 2f50d2c
(https://nightly.link/madewokherd/wine-mono/actions/artifacts/131614059.zip)
Program: Winlink Express 1.5.44.0
Radio: Yaesu FT-891 transceiver (with dummyload attached directly to radio - no
feed line so I don't accidentally send signals)
Details:
- FT-891 connected to PC via USB cable (and make sure VMWare has the USB line
routed into the VM instead of the host PC)
- I set the FT-891's on-board settings to data 'baud' 9600.
- I set in/out audio devices in ARDOP settings on the PC.
Thank you again! And here's to 2022 being better than the previous two years
:) Cheers
----
wine-mono not implemented exception log:
```
WINE_MONO_TRACE=E:System.MissingMethodException MONO_INLINELIMIT=0
WINE_MONO_HIDETYPES=1 wine RMS\ Express.exe
...
[00000024:] EXCEPTION handling: System.NotImplementedException: The method or
operation is not implemented.
"<unnamed thread>" tid=00000024 this=04570120 , thread handle : 01df5788,
state : not waiting
at System.IO.Ports.SerialPort.set_ReceivedBytesThreshold (int) [0x0000f]
in <117354a27af94c36af91c072a84e6fb8>:0
at (wrapper remoting-invoke-with-check)
System.IO.Ports.SerialPort.set_ReceivedBytesThreshold (int) [0x00032] in
<117354a27af94c36af91c072a84e6fb8>:0
at RMS_Express.Radio.OpenControlPort () [0x000b3] in
<25c56d5497bc4490bd1b5395b173c5df>:0
at RMS_Express.Radio.SetRadio () [0x0014f] in
<25c56d5497bc4490bd1b5395b173c5df>:0
at RMS_Express.Radio.SetFrequency (int,string) [0x00021] in
<25c56d5497bc4490bd1b5395b173c5df>:0
at (wrapper remoting-invoke-with-check) RMS_Express.Radio.SetFrequency
(int,string) [0x00033] in <25c56d5497bc4490bd1b5395b173c5df>:0
at RMS_Express.ArdopSession.Ardop_Activated (object,System.EventArgs)
[0x00823] in <25c56d5497bc4490bd1b5395b173c5df>:0
at System.Windows.Forms.Form.OnActivated (System.EventArgs) [0x0001f] in
<ff4fde3cd5024947a0edb51b0ef7fff6>:0
at System.Windows.Forms.Form.set_Active (bool) [0x000a6] in
<ff4fde3cd5024947a0edb51b0ef7fff6>:0
at System.Windows.Forms.Form.WmActivate (System.Windows.Forms.Message&)
[0x0001a] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0
at System.Windows.Forms.Form.WndProc (System.Windows.Forms.Message&)
[0x001b8] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0
at System.Windows.Forms.Control/ControlNativeWindow.OnMessage
(System.Windows.Forms.Message&) [0x00001] in
<ff4fde3cd5024947a0edb51b0ef7fff6>:0
at System.Windows.Forms.Control/ControlNativeWindow.WndProc
(System.Windows.Forms.Message&) [0x000b3] in
<ff4fde3cd5024947a0edb51b0ef7fff6>:0
at System.Windows.Forms.NativeWindow.Callback
(System.Windows.Forms.Message&) [0x00025] in
<ff4fde3cd5024947a0edb51b0ef7fff6>:0
at (wrapper remoting-invoke-with-check)
System.Windows.Forms.NativeWindow.Callback (System.Windows.Forms.Message&)
[0x00032] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0
at System.Windows.Forms.NativeWindowProc.Callback
(intptr,int,intptr,intptr) [0x00037] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0
at (wrapper native-to-managed)
System.Windows.Forms.NativeWindowProc.Callback (intptr,int,intptr,intptr)
<0x00067>
at <unknown> <0xffffffff>
at (wrapper managed-to-native)
System.Windows.Forms.SafeNativeMethods.ShowWindow
(System.Runtime.InteropServices.HandleRef,int) <0x00012>
at System.Windows.Forms.Control.SetVisibleCore (bool) [0x00061] in
<ff4fde3cd5024947a0edb51b0ef7fff6>:0
at System.Windows.Forms.Form.SetVisibleCore (bool) [0x000d1] in
<ff4fde3cd5024947a0edb51b0ef7fff6>:0
at System.Windows.Forms.Control.set_Visible (bool) [0x00001] in
<ff4fde3cd5024947a0edb51b0ef7fff6>:0
at System.Windows.Forms.Control.Show () [0x00001] in
<ff4fde3cd5024947a0edb51b0ef7fff6>:0
at RMS_Express.ArdopSession.ShowSession () [0x00000] in
<25c56d5497bc4490bd1b5395b173c5df>:0
at RMS_Express.Main.StartSession () [0x005fd] in
<25c56d5497bc4490bd1b5395b173c5df>:0
at RMS_Express.Main.mnuSession_Click (object,System.EventArgs) [0x00000]
in <25c56d5497bc4490bd1b5395b173c5df>:0
at System.Windows.Forms.ToolStripItem.RaiseEvent
(object,System.EventArgs) [0x0001b] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0
at System.Windows.Forms.ToolStripItem.OnClick (System.EventArgs)
[0x00001] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0
at System.Windows.Forms.ToolStripMenuItem.OnClick (System.EventArgs)
[0x0001d] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0
at System.Windows.Forms.ToolStripItem.HandleClick (System.EventArgs)
[0x00051] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0
at System.Windows.Forms.ToolStripItem.HandleMouseUp
(System.Windows.Forms.MouseEventArgs) [0x000fd] in
<ff4fde3cd5024947a0edb51b0ef7fff6>:0
at System.Windows.Forms.ToolStripItem.FireEventInteractive
(System.EventArgs,System.Windows.Forms.ToolStripItemEventType) [0x00053] in
<ff4fde3cd5024947a0edb51b0ef7fff6>:0
at System.Windows.Forms.ToolStripItem.FireEvent
(System.EventArgs,System.Windows.Forms.ToolStripItemEventType) [0x00103] in
<ff4fde3cd5024947a0edb51b0ef7fff6>:0
at (wrapper remoting-invoke-with-check)
System.Windows.Forms.ToolStripItem.FireEvent
(System.EventArgs,System.Windows.Forms.ToolStripItemEventType) [0x00033] in
<ff4fde3cd5024947a0edb51b0ef7fff6>:0
at System.Windows.Forms.ToolStrip.OnMouseUp
(System.Windows.Forms.MouseEventArgs) [0x0007d] in
<ff4fde3cd5024947a0edb51b0ef7fff6>:0
at System.Windows.Forms.Control.WmMouseUp
(System.Windows.Forms.Message&,System.Windows.Forms.MouseButtons,int) [0x001c3]
in <ff4fde3cd5024947a0edb51b0ef7fff6>:0
at System.Windows.Forms.Control.WndProc (System.Windows.Forms.Message&)
[0x005a0] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0
at System.Windows.Forms.ScrollableControl.WndProc
(System.Windows.Forms.Message&) [0x00043] in
<ff4fde3cd5024947a0edb51b0ef7fff6>:0
at System.Windows.Forms.ToolStrip.WndProc (System.Windows.Forms.Message&)
[0x00128] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0
at System.Windows.Forms.MenuStrip.WndProc (System.Windows.Forms.Message&)
[0x00056] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0
at System.Windows.Forms.Control/ControlNativeWindow.OnMessage
(System.Windows.Forms.Message&) [0x00001] in
<ff4fde3cd5024947a0edb51b0ef7fff6>:0
at System.Windows.Forms.Control/ControlNativeWindow.WndProc
(System.Windows.Forms.Message&) [0x000b3] in
<ff4fde3cd5024947a0edb51b0ef7fff6>:0
at System.Windows.Forms.NativeWindow.Callback
(System.Windows.Forms.Message&) [0x00025] in
<ff4fde3cd5024947a0edb51b0ef7fff6>:0
at (wrapper remoting-invoke-with-check)
System.Windows.Forms.NativeWindow.Callback (System.Windows.Forms.Message&)
[0x00032] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0
at System.Windows.Forms.NativeWindowProc.Callback
(intptr,int,intptr,intptr) [0x00037] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0
at (wrapper native-to-managed)
System.Windows.Forms.NativeWindowProc.Callback (intptr,int,intptr,intptr)
<0x00067>
at <unknown> <0xffffffff>
at (wrapper managed-to-native)
System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW
(System.Windows.Forms.NativeMethods/MSG&) <0x00012>
at
System.Windows.Forms.Application/ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop
(intptr,int,int) [0x001d7] in <ff4fde3cd5024947a0edb51b0ef7fff6>:0
at System.Windows.Forms.Application/ThreadContext.RunMessageLoopInner
(int,System.Windows.Forms.ApplicationContext) [0x00282] in
<ff4fde3cd5024947a0edb51b0ef7fff6>:0
at System.Windows.Forms.Application/ThreadContext.RunMessageLoop
(int,System.Windows.Forms.ApplicationContext) [0x0001a] in
<ff4fde3cd5024947a0edb51b0ef7fff6>:0
at (wrapper remoting-invoke-with-check)
System.Windows.Forms.Application/ThreadContext.RunMessageLoop
(int,System.Windows.Forms.ApplicationContext) [0x00033] in
<ff4fde3cd5024947a0edb51b0ef7fff6>:0
at System.Windows.Forms.Application.Run
(System.Windows.Forms.ApplicationContext) [0x00006] in
<ff4fde3cd5024947a0edb51b0ef7fff6>:0
at
Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnRun ()
[0x00044] in <e344caf534bf4ffb982376a141ed987b>:0
at
Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.DoApplicationModel
() [0x00035] in <e344caf534bf4ffb982376a141ed987b>:0
at
Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run
(string[]) [0x0001b] in <e344caf534bf4ffb982376a141ed987b>:0
at RMS_Express.My.MyApplication.Main (string[]) [0x0000f] in
<25c56d5497bc4490bd1b5395b173c5df>:0
at (wrapper runtime-invoke) <Module>.runtime_invoke_void_object
(object,intptr,intptr,intptr) [0x00027] in <25c56d5497bc4490bd1b5395b173c5df>:0
```
--
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=52722
Bug ID: 52722
Summary: Winetricks dotnet installation hangs at wineserver -w
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ole32
Assignee: wine-bugs(a)winehq.org
Reporter: tatidev1454(a)protonmail.com
Distribution: ---
Created attachment 72082
--> https://bugs.winehq.org/attachment.cgi?id=72082
Logs of the affected function create_surrogate_server with 32 bits wine and
WoW64
This bug only happens with 13064f991408ea5fa5e999705b13bda7bbd50e5b commit.
1. Run `winetricks dlls dotnet45` having a 32 bits build of wine in the PATH
(or
any other dotnet version which requires the installation of an older one)
2. Wait until dotnet40 installs.
3. Winetricks executes wineserver -w and it just hangs 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.
https://bugs.winehq.org/show_bug.cgi?id=52721
Bug ID: 52721
Summary: d3dx9_36:effect, d3dx11_42:d3dx11 and d3dx11_43:d3dx11
broken by use of vkd3d_shader_compile() for
D3DCompile2()
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d-util
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
A recent patch to use vkd3d_shader_compile() to implement D3DCompile2() broke
d3dx11_42:d3dx11 and d3dx11_43:d3dx11. In both cases it leads to a crash:
d3dx11.c:580: Test failed: Got unexpected errors.
Unhandled exception: page fault on read access to 0x00000000 in 32-bit code
(0x70bb0990).
[...]
Backtrace:
=>0 0x70bb0990 strrchr+0x10(str=0x000000000, c=0x5c)
[Z:\home\winetest\winetest\src\dlls\msvcrt\string.c:3166] in ucrtbase
(0x0031d9b8)
1 0x69d8bcc9 d3dcompiler_include_from_file_open+0x49(iface=<internal error>,
include_type=<internal error>, filename=<internal error>, parent_data=<internal
error>, data=<internal error>, bytes=<internal error>)
[Z:\home\winetest\winetest\src\dlls\d3dcompiler_43\compiler.c:521] in
d3dcompiler_47 (0x0031db28)
https://test.winehq.org/data/patterns.html#d3dx11_42:d3dx11https://test.winehq.org/data/patterns.html#d3dx11_43:d3dx11
d3dx9_36:effect got broken too but at least in this case it's because of
successes in todos so it's probably a trivial fix:
effect.c:8108: Test succeeded inside todo block: Unexpected error, hr
0x80004005.
effect.c:8133: Test succeeded inside todo block: D3DXInclude test failed with
error 0x80004005.
https://test.winehq.org/data/patterns.html#d3dx9_36:effect
The commit that caused these new failures is:
commit 6a062afb75c1e026614403312f2e13207e359634 (HEAD, refs/bisect/bad)
Author: Zebediah Figura <zfigura(a)codeweavers.com>
Date: Thu Mar 3 20:25:26 2022 -0600
d3dcompiler: Implement D3DCompile2() using vkd3d_shader_compile().
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=51713
Signed-off-by: Zebediah Figura <zfigura(a)codeweavers.com>
Signed-off-by: Matteo Bruni <mbruni(a)codeweavers.com>
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
--
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=52668
Bug ID: 52668
Summary: Sparx Enterprise architect v15.2 1560 crashing on wine
7.4
Product: Wine
Version: 7.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: viliam(a)tokarcik.eu
Distribution: ---
Hi,
After upgrade wine from 7.3 to 7.4 Sparx enterprise architect v15.2 1560 start
crashing while startup.
0024:err:seh:NtRaiseException Unhandled exception code c0000005 flags 0 addr
0x3c0b989
wine ~/.wine32/drive_c/Program Files/Sparx Systems/EA/EA.exe
--
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=52628
Bug ID: 52628
Summary: game frozen after opening due to infinite loop in
winmm.mmioDescend()
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winmm&mci
Assignee: wine-bugs(a)winehq.org
Reporter: l12436(a)yahoo.com.tw
Distribution: ---
Created attachment 71949
--> https://bugs.winehq.org/attachment.cgi?id=71949
fix patch for infinite loop
in winmm, mmio.c, function mmioDescend() around line 1232
there are a loop for mmioRead() mmioSeek() ...
some old game using mmioDescend() and mmioRead() has a chance that always
return -1 causing infinite loop.
My only solution now is to skip that loop when mmioRead() return -1.
This affect some old game like poppo, Silk Road ~Tale of the Star Island~ made
by Sprite
--
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=52781
Bug ID: 52781
Summary: Origin does not notice games exiting, does not allow
them to be relaunched
Product: Wine
Version: 7.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: xiretza+winehq(a)xiretza.xyz
Distribution: ---
Created attachment 72163
--> https://bugs.winehq.org/attachment.cgi?id=72163
wine log of starting origin, launching game and quitting game
Upon starting a game from Origin, the "Play" button gets grayed out and no
further games can be launched. Normally, this is supposed to revert once the
game exits, but Origin under Wine does not seem to notice this, and has to be
quit and relaunched completely to play another game (or start the original game
again).
--
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=52784
Bug ID: 52784
Summary: Double mouse cursor in Fahrenheit: Indigo Prophecy
Remastered
Product: Wine
Version: 7.5
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 72165
--> https://bugs.winehq.org/attachment.cgi?id=72165
example
wine-7.5-264-g5a815669e8e
--
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=52780
Bug ID: 52780
Summary: The Evil Within has very slow performance
Product: Wine
Version: 7.5
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 72161
--> https://bugs.winehq.org/attachment.cgi?id=72161
output
wine-7.5-264-g5a815669e8e
--
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=52530
Bug ID: 52530
Summary: dowonline: Crash at start with multiple error messages
(needs dotnet452)
Product: Wine
Version: 7.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: mscoree
Assignee: wine-bugs(a)winehq.org
Reporter: joseskvolpe(a)gmail.com
Distribution: ---
Created attachment 71830
--> https://bugs.winehq.org/attachment.cgi?id=71830
Screenshots and log
This application crashes from beginning on Wine Mono 7.0.0, installing
dotnet452 with winetricks is a working workaround
I've used the ZIP version of the application. Version 2.8
Procedure:
1 - Run DowOnline.exe
Download (Version v. 2.8):
https://dowonline.ru
SHA1 (ZIP): 101a1bf896b834cd8653127a985ae10c080dbeba
SHA1 (Installer): f47f7a529f5fcb0449fad0a5d497f667292accea
Note: I had TLS package decode errors during download, so i was unable to
download it from a browser, use wget instead to download the file if that
occurs
--
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=52532
Bug ID: 52532
Summary: SDL 2.0.20 doesn't restore fullscreen mode when
restoring a window
Product: Wine
Version: 7.1
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: winex11.drv
Assignee: wine-bugs(a)winehq.org
Reporter: madewokherd(a)gmail.com
Distribution: ---
Same testcase as bug 52519.
SDL will, in some cases, minimize fullscreen windows when they are deactivated.
If this happens in SDL 2.0.20, the window will not be fullscreen when it is
restored.
To reproduce the bug:
* Run the test program in Wine with SDL_EVENT_LOGGING=1
* Click the window to fullscreen it.
* Alt+tab to another window.
* Restore the test program's window.
* It appears with a windowed size rather than fullscreen.
Based on logs, I believe that SDL is requesting a fullscreen size and position,
but Wine never requests NET_WM_STATE_FULLSCREEN. I'm not sure why.
--
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=52519
Bug ID: 52519
Summary: SDL 2.0.20 reports wrong FOCUS_GAINED event when
minimizing an inactive fullscreen window
Product: Wine
Version: 7.1
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: madewokherd(a)gmail.com
Distribution: ---
Created attachment 71817
--> https://bugs.winehq.org/attachment.cgi?id=71817
test case (C source)
SDL will, in some cases, minimize fullscreen windows when they are deactivated.
If this happens in SDL 2.0.20, it will report a FOCUS_LOST event followed by a
FOCUS_GAINED event. It should only report the FOCUS_GAINED event when the
window is restored, which is what happens on Windows.
Also reported here: https://github.com/libsdl-org/SDL/issues/5316
Test program attached. This requires SDL.
To reproduce the bug:
* Run the test program in Wine with SDL_EVENT_LOGGING=1
* Click the window to fullscreen it.
* Alt+tab to another window.
* The last focus event logged was FOCUS_GAINED.
I know this happens because SDL receives a WM_ACTIVATE message indicating that
the window is minimized, but GetForegroundWindow reports that the application
is still in the foreground. SDL responds to WM_ACTIVATE by "resyncing" focus,
so it responds to this by reporting FOCUS_GAINED.
I haven't been able to figure out the exact set of circumstances that cause
this behavior in Wine, so I couldn't make a test case that doesn't require SDL.
--
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=52529
Bug ID: 52529
Summary: Black screen in Zork: Grand Inquisitor
Product: Wine
Version: 7.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jhansonxi(a)gmail.com
Distribution: ---
Zork: Grand Inquisitor (CD and demo version) installs without problems but
launching the game results in a black screen.
This may be related to bug 1347, bug 2082, etc. but needs to be reviewed to
determine if it is a duplicate of those or not.
Demo: https://archive.org/details/ZGIDEMO
GoG: https://www.gog.com/game/zork_grand_inquisitor
The CD version of the game is playable on ScummVM and the GoG version includes
it. The demo doesn't work (cursor only) so the other versions are more
reliable examples of expected behavior.
https://wiki.scummvm.org/index.php?title=Zork:_Grand_Inquisitor
The game requires 640x480x16. I tried it in a virtual desktop and Xephyr.
Game music requires MIDI (I used TiMidity++).
Xubuntu 20.04.3 x86_64
AMD Phenom 9550
GeForce GTX 750 Ti using Nvidia 470.57.02 driver
--
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=52662
Bug ID: 52662
Summary: Cyberpunk 2077 fails to start with LdrInitializeThunk
"comctl32.dll" failed to initialize, aborting
Product: Wine-staging
Version: 7.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: shtetldik(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
With wine-staging 7.4, Cyberpunk 2077 isn't launching anymore, with such error
showing up in the logs:
0134:err:module:LdrInitializeThunk "comctl32.dll" failed to initialize,
aborting
0134:err:module:LdrInitializeThunk Initializing dlls for
L"C:\\cyberpunk_2077\\bin\\x64\\Cyberpunk2077.exe" failed, status c0000005
I tested it with regular (non staging) Wine and it launches OK, so it must be
some regression in 7.4 staging.
--
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=52768
Bug ID: 52768
Summary: IrfanView can't open images with context menu
resulting in a black screen
Product: Wine
Version: 7.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mo78(a)abv.bg
Distribution: ---
Hello,
As of v.7.5 IrfanView can't open images from the context menu when this
workaround is used:
QUICKPARLOCATION="/path/to/i_view32.exe"
PARAM=`winepath -w "$*"`
wine "$QUICKPARLOCATION" "$PARAM" &
exit 0
The program starts normally but with a black screen instead of the image. It's
working fine with all previous Wine versions.
Without this workaround there's no context menu to open images and it isn't in
the list of available image handling programs, despite of the fact "Association
with images" is selected during install.
Executing this script doesn't give any useful output so I don't know how to
give you any.
--
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=52645
Bug ID: 52645
Summary: API PathMatchSpecExW not implemented
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: co(a)kevquinn.com
Distribution: ---
Created attachment 71964
--> https://bugs.winehq.org/attachment.cgi?id=71964
Backtrace showing PathMatchSpexExW error
The McAfee "FRP" removable media encryption client uses the PathMatchSpecExW
API, which isn't implemented, and prevents the client from running on Wine.
(McAfee don't have a native Linux client as far as I can tell)
(PathMatchSpecW is implemented - it's the Ex variant that isn't)
The API being missing means the application is killed at that point.
--
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=52766
Bug ID: 52766
Summary: broken packages during WineHQ 7 stable install on
Ubuntu 20.04
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: laszlo.a.toth(a)googlemail.com
CC: dimesio(a)earthlink.net
Distribution: ---
Created attachment 72137
--> https://bugs.winehq.org/attachment.cgi?id=72137
relevant command and error message
Hi All,
During the installation process the following last step command causes the
package dependencies problem can be seen in the attached file:
laci@sanyika:~$ sudo aptitude install winehq-stable
.
.
.
The following packages have unmet dependencies:
perl-base : Conflicts: perl-base:i386 but 5.30.0-9ubuntu0.2 is to be installed
perl-base:i386 : Conflicts: perl-base but 5.30.0-9ubuntu0.2 is installed
snmp : Conflicts: snmp:i386 but 5.8+dfsg-2ubuntu2.3 is to be installed
snmp:i386 : Conflicts: snmp but 5.8+dfsg-2ubuntu2.3 is installed
perl : Conflicts: perl:i386 but 5.30.0-9ubuntu0.2 is to be installed
perl:i386 : Conflicts: perl but 5.30.0-9ubuntu0.2 is installed
Unable to resolve dependencies! Giving up...
Please see the attachment. Thank you for your effort!
--
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=52758
Bug ID: 52758
Summary: SilkyPix Developer version 11 crashes on starting
Product: Wine
Version: 7.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: alan(a)rubin.org.uk
Distribution: ---
Created attachment 72123
--> https://bugs.winehq.org/attachment.cgi?id=72123
Backtrace produced from wine encountering serious error
I have used SilkyPix version 6 for many years under wine 32 bit.
I have now installed SilkyPix 11 in wine64. Thisprogram requires Windows 10+
and 64bit.
The installation was successful but on running the program crashes just as the
main window comes up. Backtrace 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=52634
Bug ID: 52634
Summary: err:virtual:virtual_setup_exception stack overflow and
could not load kernel32.dll when doing anything
Product: Wine
Version: 6.19
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: bill081001(a)gmail.com
Distribution: ---
Created attachment 71959
--> https://bugs.winehq.org/attachment.cgi?id=71959
Relay log of running winecfg on a new prefix
I'm on Arch Linux and my Wine installation has not been working since version
6.19
Creating a new prefix and running winecfg yields the following error:
$ rm -rf ~/.wine && ./wine winecfg
wine: created the configuration directory '/home/kuroni/.wine'
002c:fixme:actctx:parse_depend_manifests Could not find dependent assembly
L"Microsoft.Windows.Common-Controls" (6.0.0.0)
0040:err:virtual:virtual_setup_exception stack overflow 708 bytes in thread
0040 addr 0x223d656d stack 0x120d3c (0x120000-0x121000-0x320000)
002c:err:virtual:virtual_setup_exception stack overflow 1284 bytes in thread
002c addr 0x7bc510e8 stack 0x120afc (0x120000-0x121000-0x320000)
wine: could not load kernel32.dll, status c0000135
Running winecfg or any applications on the created prefix yields a similar
error:
$ ./wine winecfg
002c:fixme:actctx:parse_depend_manifests Could not find dependent assembly
L"Microsoft.Windows.Common-Controls" (6.0.0.0)
002c:err:virtual:virtual_setup_exception stack overflow 1284 bytes in thread
002c addr 0x7bc510e8 stack 0x120afc (0x120000-0x121000-0x320000)
wine: could not load kernel32.dll, status c0000135
Note that these are run on a fresh build of wine. I bisected and this is the
faulty commit:
commit f309721d13d8d728732ca97224c7502493ff6026
Author: Jacek Caban <jacek(a)codeweavers.com>
Date: Wed Oct 6 16:20:19 2021 +0200
gdi32: Use __wine_unix_call interface for Unix library.
--
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=52748
Bug ID: 52748
Summary: patch winex11_WM_WINDOWPOSCHANGING and
winex11__NET_ACTIVE_WINDOW causing some focus error
Product: Wine-staging
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: l12436(a)yahoo.com.tw
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Some game switch out of the game by using alt+tab, and switch back.
The game no longer accept input of the mouse, but the vanilla wine does not has
this issue.
After I debugging, disabling the patchset winex11_WM_WINDOWPOSCHANGING and
winex11__NET_ACTIVE_WINDOW will make it working again.
I thought maybe there are some defect in winex11__NET_ACTIVE_WINDOW patch.
--
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=52643
Bug ID: 52643
Summary: 0024:err:module:import_dll Library api-ms-*
Product: Wine
Version: 7.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: api-ms-win-*
Assignee: wine-bugs(a)winehq.org
Reporter: enni(a)telsh.de
Distribution: ---
Hi,
starting with the WINE update to 7.3 on my Manjaro distro the game "Titan
Quest" does not work anymore.
Though it crashed before the update sometimes after playing ~30 minutes, after
the update it crashed immediately when I opened the character inventory or
waited for a couple of minutes.
As I thought this might be related to something I have done or set in the
application, I deleted the whole WINEPREFIX folder and created it again plus
running "winecfg" once to update the data that is needed in the folder (without
changing anything manually).
Codewise it looks like:
$ cd $WINEPREFIX && cd ..
$ rm -rf TitanQuest
$ mkdir TitanQuest
$ winecfg
Then I did a couple of tests to get the game running again:
1) Install the game and let it install its libs and dependencies -> Game does
not start at all (as expected as fonts, codecs, etc are missing)
2) Install corefonts+tahoma, dsound and l3codecx with winetricks -> Game does
not start with "api-ms-* libraries not found"
3) Install vcrun2019 -> same as 2)
4) Install vcrun2013 -> same as 2)
I also tried to change all the libraries from "Native" to "Builtin" with
winecfg but this does not resolve the issue.
Before the update, the libraries were in the "windows/system32" folder but
right now they are not, even if I try to reinstall/repair the vcrun* packages.
As I saw that the implementation changed, I thought it might be of value to you
to get that feedback...
And as I was not able to find some documentation in the wiki that describes my
issue or how to resolve it, I'm a bit lost on how to proceed...
Thanks alot for taking the time and please reach out in case I can test some
patch etc!
Kind regards,
enni
--
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=52756
Bug ID: 52756
Summary: Unhandled exception: page fault on read access to
0x0000051b in 32-bit code (0x00931673).
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: tanuj.phd(a)gmail.com
Distribution: ---
Created attachment 72122
--> https://bugs.winehq.org/attachment.cgi?id=72122
Unhandled exception: page fault on read access to 0x0000051b in 32-bit code
(0x00931673).
HI, When I open an application ZeroBrane Studio using Wine, it give me an error
and does not allow the program to run. See attached. Thank you
--
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=52754
Bug ID: 52754
Summary: When IME is in the Composition state, the CPS_COMPLETE
event does not occur when clicking the mouse.
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: richedit
Assignee: wine-bugs(a)winehq.org
Reporter: take-me-home(a)kakao.com
Distribution: ---
When IME is in the Composition state, the CPS_COMPLETE event does not occur
when clicking the mouse.
Therefore, when move the cursor, the text in the Composition state is inserted
into the new cursor position.
As a normal operation, should inform IME that Composition has been completed
and handle events related to click buttons after completing IME operations.
--
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=52753
Bug ID: 52753
Summary: Embrilliance: Cursor disappears when trying to
draw/edit stitches in create mode.
Product: Wine
Version: 7.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jmyles57(a)gmail.com
Distribution: ---
Created attachment 72121
--> https://bugs.winehq.org/attachment.cgi?id=72121
Image of buttons to press to recreate issue
Requires any Embrilliance module that lets you interact with the stitches.
(Such as Stitch Artist).
To reproduce:
1) Click the 'Create' button
2) Click any tool that allows you to draw on the canvas
3) Move cursor to the canvas, mouse cursor disappears.
Software otherwise works excellent with Wine!
--
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.
https://bugs.winehq.org/show_bug.cgi?id=52614
Bug ID: 52614
Summary: 002c:err:module:load_apiset_dll failed to load apiset:
c0000482
Product: Wine
Version: 7.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wineserver
Assignee: wine-bugs(a)winehq.org
Reporter: mahg361(a)gmail.com
Distribution: ---
$ WINEPREFIX="/home/m/.wine" WINEARCH=win64 wine64 wineboot
wine: created the configuration directory '/home/m/.wine'
002c:err:module:load_apiset_dll failed to load apiset: c0000482
002c:fixme:actctx:parse_depend_manifests Could not find dependent assembly
L"Microsoft.Windows.Common-Controls" (6.0.0.0)
0034:err:module:load_apiset_dll failed to load apiset: c0000482
0040:err:module:load_apiset_dll failed to load apiset: c0000482
0048:err:module:load_apiset_dll failed to load apiset: c0000482
.
.
.
It happens only with wine64
I installed wine using Arch Linux official repo
--
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=52727
Bug ID: 52727
Summary: Access to window.external in an embedded browser
breaks javascript
Product: Wine
Version: 5.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ieframe
Assignee: wine-bugs(a)winehq.org
Reporter: sergey.bychkow(a)gmail.com
Distribution: ---
I'm not sure that this is problem for ieframe, or shdocw, or gecko component,
but when javascript in an embedded browser tries to access custom
window.external object defined with an implementation of
IDocHostUIHandler.GetExternal() then javascript fails to proceed. The call of
GetExternal() function returns successfully.
A javascript code looks like:
{script}
document.write('external: ');
var obj2 = window.external; -- next lines won't execute on Wine, but work on
Wndws
document.write(obj2);
document.write('<br>');
var obj3 = window.external.myProperty;
{/script}
Embedding is done like in the article:
https://delphidabbler.com/articles/article-22
TODO: Make isolated test case if information is not enough.
--
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=52745
Bug ID: 52745
Summary: ATPDraw not showing title bar
Product: Wine
Version: 7.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: hildogjr(a)gmail.com
Distribution: ---
Created attachment 72112
--> https://bugs.winehq.org/attachment.cgi?id=72112
After open (not maximized)
The fix
https://bugs.winehq.org/show_bug.cgi?id=52675
worked fine, but the software do not shows the title bar when maximized. See
the attached images.
Useful information:
Linux Ubuntu 20.04.4 LTS x64
GNOME Version 3.36.8
Windowing System X11
Graphics NV118 / Mesa Intel® HD Graphics 620 (KBL GT2)
--
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=52746
Bug ID: 52746
Summary: Minecraft Windows bedrock server needs chakra.dll
Product: Wine
Version: 7.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mowinebugs(a)mail.com
Distribution: ---
Created attachment 72114
--> https://bugs.winehq.org/attachment.cgi?id=72114
terminal output
Download link: https://www.minecraft.net/en-us/download/server/bedrock
--
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=52710
Bug ID: 52710
Summary: Line wrapping with newlines in command line tool
output (ISCC.exe)
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: 20220321.winehq.org(a)darkart.com
[This was discovered using CrossOver by CodeWeavers, going from version 20.0.4
to 21.1.0 and CodeWeavers has asked me to open a bug here for it.]
Output from the command line tool "ISCC.exe" (part of the InnoSetup tools) now
has extra newlines that are doing line wrapping. Unfortunately this breaks up
words in the output which impedes our parsing of the output.
Example output when running under wine from CrossOver 21.1.0:
\r\r\n\u001b[?25h\u001b[?25lCopyright (C) 2001-2004 Alex Yackimoff. All rights
reserved.\r\r\n\u001b[?25h\r\r\n\u001b[?25lCompiler engine version: Inno Setup
5.5.9 (u)\r\r\n\u001b[?25h\r\r\n\u001b[?25l[ISPP]
Preprocessing.\r\r\n\u001b[?25h\u001b[?25l[ISPP]
Preprocessed.\r\r\n\u001b[?25h\r\r\n\u001b[?25lParsing [Setup] section, line
28\r\r\n\u001b[?25h\u001b[?25lParsing [Setup] section, line 29\r\r\n\u001b[?25h
I believe the "[?25h" and "[?25l" are escape sequences that were not present
when running under CrossOver 20.0.4.
The '\r' and '\n' characters are showing up in what used to be single-line
text, like:
Using an external code-signing tool, pleas\r\r\ne attach your digital signature
to the following executable file
Note how the word "please" has been fragmented.
--
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=52744
Bug ID: 52744
Summary: Cisco Jabber 12.x/14.x chat window not displayed
correctly
Product: Wine
Version: 7.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: winehq(a)georg-sieber.de
Distribution: ---
Created attachment 72108
--> https://bugs.winehq.org/attachment.cgi?id=72108
Broken Chat Window of Cisco Jabber
Cisco Jabber generally works very well with the latest wine versions, only one
problem persists: the chat window does not display properly.
Mostly, the chat window is black or white, only sometimes it shows the expected
chat messages for a short time (please have a look at the screenshot attached).
The about window seems to have the same issue. So you can also reproduce it by
opening this dialog (using the settings menu), no need to log in into 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.
https://bugs.winehq.org/show_bug.cgi?id=52730
Bug ID: 52730
Summary: Reading Rabbit Playtime Baby shows black screen
Product: Wine
Version: 7.4
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: bashninja(a)801labs.org
Distribution: ---
Created attachment 72091
--> https://bugs.winehq.org/attachment.cgi?id=72091
256 Color Mode
The install of this game fails when you install inside a 64bit wine bottle. It
shows an error about disk space. This is resolved by installing with a 32bit
wine bottle and using winecfg to switch the windows version to "Windows 98". If
you do this, it allows you to install the game successfully.
After the game is installed and launched, it loads to a black screen. You can
hear audio and click things, but there is nothing to see.
You can get it working a tiny bit in 256 color mode, but it doesn't look right
at all. I attached a screenshot of that.
Instructions to Reproduce:
Set up a 32bit wine bottle and, with winecfg, set the windows version to
"Windows 98".
This game needs to have the disk mounted in linux as a CD-ROM. To do this, I
installed and used cdemu. You can find details about this application here:
https://wiki.archlinux.org/title/CDemu . The way I used this tool was by
installing cdemu-daemon & I used kde-cdemu-manager as the gui interface to that
daemon. I then mounted the downloaded .cue file.
After mounting the .cue file, you should see something similar to this in your
mounts:
$ mount | grep sr0
/dev/sr0 on /run/media/bashninja/RRBaby type iso9660
Now you should be able to run the Setup.exe and get through the install without
any issues.
$ WINEARCH="win32" WINEPREFIX=~/.wine32_RRB wine D:\Setup.exe
(D:\ should match the path to your mounted CD-ROM)
After the install, you can launch Setup.exe again and you'll be able to launch
the game. You'll hear the music and be able to click, but the screen will be
black. You'll also get a wonderful new desktop icon.
To test 256 color mode, you can follow these instructions after the game has
been installed:
https://wiki.winehq.org/256_Color_Mode
--
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=52736
Bug ID: 52736
Summary: Argentum 20 RPG Launcher has graphical glitches when
compiled with -O2
Product: Wine
Version: 7.3
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dark.shadow4(a)web.de
Distribution: ---
Split of from bug 52729. Aside from the there mentioned regression, there still
are graphical glitches. See screenshots. Although those only seem to happen
when compiling with -O2, -O0 doesn't reproduce them.
--
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=52649
Bug ID: 52649
Summary: "Logitech Options" can't install
Product: Wine
Version: 7.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: martial.braux(a)gmail.com
Distribution: ---
Created attachment 71969
--> https://bugs.winehq.org/attachment.cgi?id=71969
backtrace generated
The installer of "Logitech Options" loads and crashes when reaching 100%.
The result is the backtrace 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=52739
Bug ID: 52739
Summary: DoNotSpy10 5.3 crashes after opening
Product: Wine
Version: 7.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mikrutrafal(a)protonmail.com
Distribution: ---
Created attachment 72105
--> https://bugs.winehq.org/attachment.cgi?id=72105
Full Crash log
```
=================================================================
Native Crash Reporting
=================================================================
Got a UNKNOWN while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================
=================================================================
Managed Stacktrace:
=================================================================
=================================================================
wine: Unhandled page fault on write access to 0000000000000000 at address
000000001288E091 (thread 0708), starting debugger...
...
=>0 0x000000001288e091 EntryPoint+0x7cee1() in xul (0x000000001c65f020)
1 0x0000000014b71300 EntryPoint+0x2360150() in xul (0x000000001c65f020)
2 0x0000000014b752f8 EntryPoint+0x2364148() in xul (0x000000001c65f020)
3 0x0000000014b9a0b0 EntryPoint+0x2388f00() in xul (0x000000001c65f020)
4 0x0000000014b9ec75 EntryPoint+0x238dac5() in xul (0x000000001c65f020)
5 0x0000000014b9e9a6 EntryPoint+0x238d7f6() in xul (0x000000001c65f020)
6 0x0000000014ba200e EntryPoint+0x2390e5e() in xul (0x000000001c65f020)
7 0x0000000014ba206d EntryPoint+0x2390ebd() in xul (0x000000001c65f020)
8 0x0000000010872dcf detach_gecko_browser+0x10f(This=000000000F541B00)
[Z:\usr\src\packages\BUILD\dlls\mshtml\nsembed.c:2352] in mshtml
(0x000000001c65f020)
9 0x00000000107c24cf NtCurrentTeb(This=0000000000000000)
[Z:\usr\src\packages\BUILD\include\winnt.h:2157] in mshtml (0x000000001c65f020)
10 0x00000000107c24cf GetProcessHeap(This=<register R12 not accessible in
this frame>) [Z:\usr\src\packages\BUILD\dlls\mshtml\htmldoc.c:5860] in mshtml
(0x000000001c65f020)
11 0x00000000107c24cf heap_free(This=<register R12 not accessible in this
frame>) [Z:\usr\src\packages\BUILD\dlls\mshtml\htmldoc.c:5860] in mshtml
(0x000000001c65f020)
12 0x00000000107c24cf HTMLDocumentObj_Release+0x17f(iface=<register RBX not
accessible in this frame>)
[Z:\usr\src\packages\BUILD\dlls\mshtml\htmldoc.c:5860] in mshtml
(0x000000001c65f020)
13 0x000000006f50683f deactivate_document+0x17f(This=<register RBX not
accessible in this frame>)
[Z:\usr\src\packages\BUILD\dlls\ieframe\dochost.c:572] in ieframe
(0x000000001c65f020)
14 0x000000006f51e0bb OleObject_SetClientSite+0x26b(iface=<register RBX not
accessible in this frame>, pClientSite=<internal error>)
[Z:\usr\src\packages\BUILD\dlls\ieframe\oleobject.c:498] in ieframe (0x00000
0001c65f020)
```
Steps to reproduce:
- Download and install app
- Change windows version to 10
- Run app
- After while(1-5s) app should 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=52740
Bug ID: 52740
Summary: Dragon NaturallySpeaking 13 does not install with
msiobj and msi_get_property errors
Product: Wine
Version: 7.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: msi
Assignee: wine-bugs(a)winehq.org
Reporter: susancragin(a)earthlink.net
Distribution: ---
Created attachment 72106
--> https://bugs.winehq.org/attachment.cgi?id=72106
MSI trace last 1000 lines
I have version 7.5 (Staging) running under Gentoo
Dragon NaturallySpeaking 13 does not install. I have been playing with the
installation a bit, and have seen what look like MSI errors so I ran an MSI
trace.
There is a missing msi_get_property action also.
It looks to me like something may be missing from the system.ini file??
--
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.
https://bugs.winehq.org/show_bug.cgi?id=52731
Bug ID: 52731
Summary: After a few minutes of normal operation Trails of Cold
Steel will crash from a page fault
Product: Wine
Version: 7.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: pehex66707(a)jo6s.com
Distribution: ---
Created attachment 72094
--> https://bugs.winehq.org/attachment.cgi?id=72094
Wine backtrace
The Legend of Heroes: Trails of Cold Steel I runs fine for a few minutes but
then crashes. I am using the GOG version 1.6 on Arch Linux with an nVidia
graphics card.
--
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=52734
Bug ID: 52734
Summary: Rockstar Game Launcher bag
Product: Wine
Version: 7.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jon9097(a)gmail.com
Distribution: ---
Created attachment 72095
--> https://bugs.winehq.org/attachment.cgi?id=72095
Scr
In Rockstar Game Launcher, the interface becomes black if it is overlapped by
another window. If you minimize and maximize it, it shows up again, but if you
overlap it with another window, it becomes a black rectangle again.
--
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=52733
Bug ID: 52733
Summary: Wine not in correct resolution in windows mode +
cannot move window above half screen
Product: Wine
Version: 7.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: backspacestud(a)tutanota.com
Distribution: ---
I am attempting to play Leauge of legends on linux and until recently it has
worked perfectly in windowed mode. For some reason, as of late the actual game
window launches in a 2540x1080 in staid of 2560x1440 windowed, and stays below
half of my screen, making it really squished and hard to play. I was only able
to get an error once and now i cant get it anymore, but here it is:
X Error of failed request: BadWindow (invalid Window parameter)
Major opcode of failed request: 10 (X_UnmapWindow)
Resource id in failed request: 0x3e00001
Serial number of failed request: 3693
Current serial number in output stream: 3694
: I don't know how it got this way but i was messing with drivers for a while
to get other things working and im on Wayland.
I have an AMD GPU with mesa drivers and pro open cl drivers installed.
Sorry if this is not enough information, its my first post. Thank you.
--
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=52305
Bug ID: 52305
Summary: The gog launcher
Product: Wine
Version: 7.0-rc1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jon9097(a)gmail.com
Distribution: ---
The gog launcher is very slow and errors are popping up. Please make it not
slow down.
You can download it for free from the official site and make sure it is very
slow.
--
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=52717
Bug ID: 52717
Summary: dxgi:dxgi fails because DXGI_STATUS_OCCLUDED != S_OK
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
dxgi:dxgi fails on Windows 7 and in the 64-bit Windows 8.1 because
DXGI_STATUS_OCCLUDED != S_OK:
dxgi.c:2128: Test failed: Got unexpected hr 0x87a0001.
dxgi.c:3576: Test failed: Got unexpected hr 0x87a0001.
https://test.winehq.org/data/patterns.html#dxgi:dxgi
This is because of the commit below changed a couple of SUCCEEDED(hr) to hr ==
S_OK:
commit 65ff2098826bb9944b872251b1c9543bbbe6f488
Author: Eric Pouech <eric.pouech(a)gmail.com>
AuthorDate: Fri Mar 18 16:59:29 2022 +0100
dxgi/tests: Build without -DWINE_NO_LONG_TYPES.
Signed-off-by: Eric Pouech <eric.pouech(a)gmail.com>
Signed-off-by: Henri Verbeet <hverbeet(a)codeweavers.com>
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
So the question is: should these two checks be reverted to SUCCEEDED(hr), or
should we investigate why we get DXGI_STATUS_OCCLUDED on w7pro64-64, w7u*,
win81_cw-gtx560-64 and win81_cw-rx460-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=52623
Bug ID: 52623
Summary: Crash of `not_dll` test from `windows-rs` due missing
implementation of `winspool.drv.GetSpoolFileHandle`
Product: Wine
Version: 7.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mikrutrafal(a)protonmail.com
Distribution: ---
This test pass on Windows 10
Failures
```
wine: Call from 000000017002D6A8 to unimplemented function
winspool.drv.GetSpoolFileHandle, aborting
wine: Unimplemented function winspool.drv.GetSpoolFileHandle called at address
000000017002D6A8 (thread 0340), starting debugger...
```
Rust for Windows can be installed via
https://forge.rust-lang.org/infra/other-installation-methods.html
or directly
https://static.rust-lang.org/dist/rust-1.59.0-x86_64-pc-windows-gnu.msihttps://github.com/microsoft/windows-rs/blob/master/crates/tests/not_dll/te…
Steps to reproduce
git clone https://github.com/microsoft/windows-rs.git
cd windows-rs
git checkout 9965e3c44829d0c86b2d9d2b3c5338376f158bde
cd crates/tests/not_dll/
wine cargo test
--
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.