https://bugs.winehq.org/show_bug.cgi?id=54238
Bug ID: 54238
Summary: Wine can't map file with exec priv on real CDROM
Product: Wine
Version: 8.0-rc2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: tuxifan(a)posteo.de
Distribution: ---
During Fresh Minder installation, wine attempts to map a file with EXEC
privilege into memory, causing an icon to fail to load. This can be solved by
the user by remounting the cdrom with exec privilege, but Wine should handle
this on its own (for instance by making an internal copy of the file in a place
where EXEC is possible).
--
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=29937
Bug #: 29937
Summary: File selection dialog view shows Favorites when you
click elsewhere
Product: Wine
Version: 1.4-rc1
Platform: x86-64
URL: http://www.winuae.net/files/InstallWinUAE2330.exe
OS/Version: Linux
Status: UNCONFIRMED
Severity: trivial
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: markk(a)clara.co.uk
Classification: Unclassified
There is a small issue with file selection dialogs which some programs use.
When the dialog opens, it shows the files in some directory in the right pane,
and a tree view of the directory hierarchy in the left pane. The tree view
shows Favorites and Desktop (which is expanded to show My Computer, My
Documents, Trash, /).
If you then click on any of the + or - symbols in the tree view, the view in
the right pane jumps to Favorites. For example, click the + next to My Computer
and the view on the right changes to Favorites (which may be empty).
The directory shown in the right pane should probably not change when the user
clicks a + or - symbol in the left pane.
WinUAE is one program which uses that type of file dialog. To show the problem,
download and run the WinUAE installer, check the box to run the program at the
end. When the WinUAE Properties window appears, click "Select image file" to
open a file selection dialog.
--
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=49882
Bug ID: 49882
Summary: Overdrive audio book app will not start. Worked fine
in WINE version 5.0.1
Product: Wine
Version: 5.0.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ben.miller.5150(a)gmail.com
Distribution: ---
Created attachment 68225
--> https://bugs.winehq.org/attachment.cgi?id=68225
backtrace.txt produced when Overdrive fails
Overdrive app is no longer working in WINE 5.0.2. It has only stopped working
since upgrading WINE from 5.0.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=51234
Bug ID: 51234
Summary: user32:clipboard test_ClipboardOwner() has a race
condition with clipboard managers
Product: Wine
Version: 6.8
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
test_ClipboardOwner() has a race condition with clipboard managers that causes
this set of failures:
clipboard.c:404: Test failed: SetClipboardData succeeded
clipboard.c:406: Test failed: wrong error 3735928559
clipboard.c:407: Test failed: SetClipboardData succeeded
Fortunately(?) this failure is pretty rare.
What happens is this:
* test_ClipboardOwner() does this:
OpenClibpoard(NULL)
EmptyClipboard() // take ownership
CloseClipboard()
* Then the clipboard manager starts checking the content of the clipboard:
OpenClipboard(manager_hwnd)
...
* And then the next test_ClipboardOwner() test happens:
SetClipboardData(CF_WAVE, ...)
ok(GetLastError() == ERROR_CLIPBOARD_NOT_OPEN, ...)
ok(!IsClipboardFormatAvailable(CF_WAVE), ...
Because test_ClipboardOwner() opened the clipboard with a NULL windows handle,
EmptyClipboard() used that as the clipboard owner. But when the owner is NULL a
process can place data in the clipboard as long as any process opened it. This
is actually the whole point of the run_process("set_clipboard_data 4") test.
So the problem is that user32:clipboard assumes that no other process is going
to open the clipboard after it called CloseClipboard(). Yet that's precisely
when clipboard manager would receive a WM_CLIPBOARDUPDATE message and open it.
--
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=54055
Bug ID: 54055
Summary: winhttp:winhttp times out in Wine on fg-deb64
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: winhttp
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
Created attachment 73608
--> https://bugs.winehq.org/attachment.cgi?id=73608
winhttp: Set the default DNS resolution timeout to infinite.
winhttp:winhttp started timing out on 2022-11-24 in Wine on fg-deb64:
...
winhttp.c:5215: IEProxy.ProxyBypass=(null)
winhttp:winhttp:0250 done (258) in 120s 1133B
See https://test.winehq.org/data/patterns.html#winhttp:winhttp
As far as can tell the timeout started with the commit below:
commit cbfe940a1eaf5e158de3127b1265462bfbfb70af
Author: Paul Gofman <pgofman(a)codeweavers.com>
Date: Wed Nov 23 15:36:19 2022 -0600
winhttp: Set name resolution timeout in download_script().
I'm not totally sure because the failure is not actually 100% reproducible and
gave some bad results a couple of times. But having it point at this commit
makes sense.
+ WinHttpSetTimeouts( ses, 5000, 60000, 30000, 30000 );
The timeouts disappeared when I changed the resolve timeout from 5000 ms to 0
(no timeout). So... I have a slow DNS setup? That may actually be true since
it's somewhat complicated.
But then the documentation also says that the default DNS resolve timeout is 0.
So maybe the attached patch would make sense?
Also I cannot reproduce the failure anymore. Maybe whatever name we're querying
has been thoroughly cached by all intermediate DNS servers by now. So I should
probably try that again when the DNS cache is cleared.
--
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=53919
Bug ID: 53919
Summary: crypt32:cert - testVerifyRevocation() uses an outdated
certificate
Product: Wine
Version: 7.21
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: crypt32
Assignee: wine-bugs(a)winehq.org
Reporter: jinoh.kang.kr(a)gmail.com
CC: fgouget(a)codeweavers.com, hans(a)meelstraat.net
Distribution: ---
crypt32:cert - testVerifyRevocation() fails in Wine:
cert.c:4191: Test failed: success
cert.c:4192: Test failed: got 00000000
cert.c:4193: Test failed: got 00000000
https://testbot.winehq.org/JobDetails.pl?Key=126125
The failures started on 2022-11-14 and are consistently reproducible since
then. The actual test was introduced on 2022-05-24 in the commit below.
So this is not a regression but instead looks like an outside change that broke
the test.
commit 74832c2177808c6222d44f7e4580de84e0ada8f0
Author: Hans Leidekker <hans(a)codeweavers.com>
AuthorDate: Tue May 24 09:46:22 2022 +0200
crypt32/tests: Add more OCSP revocation tests.
Signed-off-by: Hans Leidekker <hans(a)codeweavers.com>
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
The commit introduces a variable named ocsp_cert_revoked that contains the
following certificate:
Certificate:
Data:
Version: 3 (0x2)
Serial Number:
0d:2e:67:a2:98:85:3b:9a:54:52:e3:a2:85:a4:57:2f
Signature Algorithm: sha256WithRSAEncryption
Issuer: C = US, O = DigiCert Inc, CN = RapidSSL TLS DV RSA Mixed SHA256
2020 CA-1
Validity
Not Before: Oct 27 00:00:00 2021 GMT
Not After : Oct 27 23:59:59 2022 GMT
Subject: CN = revoked.badssl.com
Subject Public Key Info:
Public Key Algorithm: rsaEncryption
Public-Key: (2048 bit)
Modulus:
00:b0:76:2d:55:66:dc:72:8a:a0:9e:85:92:38:7f:
5b:e1:93:8d:ad:06:c8:ad:e9:89:b4:ef:1e:77:5b:
33:45:16:60:7d:33:38:68:04:d7:c9:83:42:83:d9:
30:4b:54:49:14:ca:ed:be:0c:76:ba:5f:a6:5c:33:
78:3f:39:f2:49:a8:88:32:ee:53:21:14:d3:aa:5c:
58:3c:39:cc:f7:80:b1:27:1f:54:79:7b:6c:8b:ff:
41:aa:39:24:95:5f:71:bc:49:bf:39:3b:a5:d5:e1:
a5:de:1d:40:81:25:dc:8a:47:82:fe:cd:7c:4b:2c:
04:bb:d3:27:56:51:a0:61:f2:d2:cb:55:08:25:2a:
85:db:2c:06:8d:0d:61:c2:5b:3e:9b:46:dc:58:ff:
13:27:be:0a:44:1e:68:fe:e1:f6:b7:de:9f:8e:6c:
c4:b5:19:fa:d7:d3:4f:55:a8:61:79:db:61:2f:6a:
9c:2c:f1:c4:81:bb:9e:d2:02:05:ba:9c:14:a0:f9:
f3:54:79:7d:69:d9:ba:66:1c:87:95:41:50:0e:f9:
5e:e1:b7:bd:f5:31:24:c5:21:21:03:8a:cf:6d:78:
58:de:d9:30:7d:03:42:52:d6:b0:1b:b9:c9:54:1b:
5a:e8:c8:53:f0:ac:2b:82:10:27:a6:a9:70:25:ae:
f8:a7
Exponent: 65537 (0x10001)
X509v3 extensions:
X509v3 Authority Key Identifier:
A4:8D:E5:BE:7C:79:E4:70:23:6D:2E:29:34:AD:23:58:DC:F5:31:7F
X509v3 Subject Key Identifier:
B0:C8:CE:20:B2:78:CC:1D:23:EF:F0:FE:D6:0E:29:4B:AC:15:72:3C
X509v3 Subject Alternative Name:
DNS:revoked.badssl.com
X509v3 Key Usage: critical
Digital Signature, Key Encipherment
X509v3 Extended Key Usage:
TLS Web Server Authentication, TLS Web Client Authentication
X509v3 CRL Distribution Points:
Full Name:
URI:http://crl3.digicert.com/RapidSSLTLSDVRSAMixedSHA2562020CA-1.crl
Full Name:
URI:http://crl4.digicert.com/RapidSSLTLSDVRSAMixedSHA2562020CA-1.crl
X509v3 Certificate Policies:
Policy: 2.23.140.1.2.1
CPS: http://www.digicert.com/CPS
Authority Information Access:
OCSP - URI:http://ocsp.digicert.com
CA Issuers -
URI:http://cacerts.digicert.com/RapidSSLTLSDVRSAMixedSHA2562020CA-1.crt
X509v3 Basic Constraints:
CA:FALSE
(snip)
The time of first failure is past the expiry date of the certificate above.
It appears that the OCSP provider has retracted the certificate entry in
question, which is no longer necessary.
--
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=48911
Bug ID: 48911
Summary: Check for compilation warnings
Product: Wine-Testbot
Version: unspecified
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
Compiling Wine with -Werror is troublesome because it applies blindly to both
wine-devel patches and patches submitted manually via the website. The sole
purpose of the latter is often to just clarify some point for the development
of another patch and are not meant to be submitted. Thus failing on warnings
just makes running these quick tests more cumbersome.
So the best way forward would be for the TestBot to identify and report
warnings but not fail the compilation and abort the tests when they occur.
So:
1. The builds should happen without -Werror.
2. GetLogLineCategory() should identify the warnings and add them to LogInfo
but distinguish them from errors (replace IsNew with a Category field?).
3. Compare task.log to the reference build log to distinguish new warnings from
old ones. This is necessary in case the compiler used by the TestBot produces
warnings on the unpatched Wine tree. It will require storing the build logs in
latest/ just like the TestBot already does for the reference WineTest reports.
4. LogInfo's will need to keep track of the number of new warnings which really
means renaming the 'NewCount' field to avoid confusion.
5. The warnings should be saved in the errors files. The new line types could
be 'w' and 'W' for old and new warnings respectively (then it would make sense
to use e and E for errors).
6. This will let the WineRun*() scripts know about both warnings and errors.
They can then decide what to do depending on the type of job and whether the
warnings are new or not.
- Old warnings would always be ignored.
- If a build task has new warnings, instead of marking it as 'badbuild' it
could be marked as 'completed' as usual but with a non-zero number of failures.
This would probably allow running the tests on Windows but the patch would
still be considered bad since the job would end up with a non-zero number of
failures.
- For Wine tasks the number of warnings would be added to the Failures field
for the same overall result.
- So in both cases the non-zero number of failures would only impact
wine-devel patches.
7. The JobDetails page should show the warnings in summary mode and highlight
them in the full build log. That would make it easy for developers to see the
warnings on web-submitted jobs, and thus fix them before submitting the patch
to wine-devel.
--
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=43653
Bug ID: 43653
Summary: Waves Central: install vst plugins issue
Product: Wine
Version: 2.16
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: viking991(a)gmx.de
Distribution: ---
Created attachment 59080
--> https://bugs.winehq.org/attachment.cgi?id=59080
waves central error message
Hi!
Waves Central (license manager / installer from waves.com) does not install vst
plugins in Wine.
installation aborts with this message box, also see attachment
###
Sorry
An error has occurred during installation
Please follow the steps in this troubleshooter
###
- System:
winehq-staging 2.16
debian stretch
- Steps to re-produce:
1) Download Waves Central installer
http://www.waves.com/downloads/central
Direct download link:
http://www.waves.com/dlrdr?id=central-win
Tested Waves Central Version: V1.3.3.4
sha1sum Install_Waves_Central.exe
0f90b9333855a8713e3f9ced767369364a46aa33 Install_Waves_Central.exe
2) Run Installer
wine64 Install_Waves_Central.exe
3) Run Waves Central
wine64 Waves\ Central.exe
4) Log in
unfortunately this needs an account with waves.com:
-> Log in -> create account -> web browser opens to create account
user user/pass in Waves Central to log in.
5) install any VST:
-> install products
-> install from online
-> choose products to install -> All Waves products
-> select any product, for example H-Reverb Hybrid Reverb 9
-> click install, message box as attached appears.
also check bug 43648
Thanks!
--
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=42588
Bug ID: 42588
Summary: Vietcong - graphics glitches since Wine 2.1
Product: Wine
Version: 2.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: havran.jan(a)email.cz
Distribution: ArchLinux
Created attachment 57517
--> https://bugs.winehq.org/attachment.cgi?id=57517
Vietcong - terminal log
In version 2.1 was introduced new bug that causes graphical glitches like
flickering soldiers. I can confirm this bug in wine versions 2.1, 2.2 and 2.3.
In versions 2.0 and below it worked probably fine - this bug is not 100%
reproducible - sometimes soldiers are flickering and glitches are shown very
often, sometimes just for few milisecond, but i am pretty sure that this was
introduced in version 2.1
Tested on Intel and AMD GPUs, Vietcong 1.60 with VCStarter 1.7 Beta
--
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=54205
Bug ID: 54205
Summary: Actua Golf 2: Installer crashes
Product: Wine
Version: 7.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: odecif(a)gmail.com
Distribution: ---
Created attachment 73743
--> https://bugs.winehq.org/attachment.cgi?id=73743
Installer console log in 32-bit prefix
Executing either autorun.exe or setup.exe makes wine crash instantly. If trying
to run Golf2.exe directly from the CD a popup shows stating I need at least
16MB of RAM, which might be related to this
https://www.zeus-software.com/forum/viewtopic.php?t=584.
I've tested with both 64 and 32bit prefixes in windows versions 95, 98, 2000,
XP, 7, 8, 10 with the same results.
I've tested the CD on a windows XP VM and it installs and runs as expected
there so there is no issue with the media itself.
If more logs are needed I'll happily provide them, just let me know.
--
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=54282
Bug ID: 54282
Summary: Allow winecfg create a prefix without mime
associations and no linked folders integration
Product: Wine
Version: 8.0-rc3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: shtetldik(a)gmail.com
Distribution: ---
By default when creating a prefix, winecfg will try to enable mime files
association and folders integration which can then be disabled explicitly.
I prefer to create a prefix with specific Windows version out of the box,
passing /v win10 for example. But that creates a ton of .desktop and mime files
for associations. It becomes a chore when creating a prefix to clean them out
every time.
It would be neat to have some parameter for winecfg that will disable mime
files associations and desktop folders integration out of the box making
creating a neat prefix with one command doable.
Something like
WINEPREFIX='/.../foo' winecfg /v win10 /nomime /nofolders
--
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=50218
Bug ID: 50218
Summary: Unable to finish the installation of Lego Staunt
rallye: request for indeo codec
Product: Wine
Version: 5.22
Hardware: x86
URL: https://www.myabandonware.com/game/lego-stunt-rally-bd
5#download
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jeremielapuree(a)yahoo.fr
Distribution: Ubuntu
Created attachment 68723
--> https://bugs.winehq.org/attachment.cgi?id=68723
screenshot of the error
At the end of the stage of install, setup complains about indeo codecs.
--
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=53619
Bug ID: 53619
Summary: World of Warcraft Shadowlands randomly crashes
Product: Wine
Version: 7.16
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: cianuro2036(a)protonmail.com
Distribution: ---
This is something that has happened on multiple hardware, platforms and OS
distros. This is also something that has been happening for a while, I just
decided to report it because It can affect some parts of the game, such as
rated PVP.
The particular error logs as follows:
05f4:err:seh:dispatch_exception unknown exception (code=c0000420) raised
wineserver crashed, please enable coredumps (ulimit -c unlimited) and restart.
How to reproduce:
This feels 'random' but makes me _think_ it could be a memory leak issue. If
you're in highly populated areas _or_ highly demanding zones, it can trigger
itself.
Two recent scenarios I can recall
- First, doing multiple arena matches and waiting for the queue in Oribos. The
crash happened specifically during arena.
- Second, doing the Ashran Brawl Battleground. This battleground is very, very
long and has a lot of people around.
In both scenarios there is a slowdown in FPS in both areas.
--
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=54278
Bug ID: 54278
Summary: Megami Ibunroku Persona doesn't open at all.
Product: Wine-staging
Version: 7.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: zanehj10(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 73844
--> https://bugs.winehq.org/attachment.cgi?id=73844
Console log
Wine just seems to immediately close with no generated errors.
Information on the game that might be useful:
Game uses DirectX 6 Graphics API.
Game uses Windows Media Player for playing FMVs.
--
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=53403
Bug ID: 53403
Summary: winegstreamer "flush" removal breaks radio in fallout
3
Product: Wine
Version: 7.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winegstreamer
Assignee: wine-bugs(a)winehq.org
Reporter: zlice(a)dflies.us
Distribution: ---
https://gitlab.winehq.org/wine/wine/-/merge_requests/105#note_4805https://gitlab.winehq.org/wine/wine/-/commit/5144b27661fcd6705353d832e03830…
In Wine 7.2 or 7.3 there was a removal of "flush" in wg_parser.
This makes some audio (in particular Fallout 3 Radio) chuggy and slows down the
entire game.
Reintroducing flushing fixes the issue but devs think the problem should be
fixed elsewhere.
--
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=44230
Bug ID: 44230
Summary: SlingPlayer 1.5 crashes during configuration
Product: Wine
Version: 2.22
Hardware: x86
URL: http://download.slingmedia.com/player/pc/SlingPlayer-S
etup-EU-1.5.1.343.exe
OS: Linux
Status: NEW
Keywords: download, regression
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: imwellcushtymelike(a)gmail.com
CC: julliard(a)winehq.org
Regression SHA1: 01676c5dd6f9fb61b9c4e52595f6e75e21050009
Distribution: Ubuntu
Created attachment 60025
--> https://bugs.winehq.org/attachment.cgi?id=60025
Wine 3.0-rc3 console output
SlingPlayer 1.5 crashes when attempting to configure the Slingbox (Alt+E -->
Slingbox Configuration --> Change...) (Slingbox needed)
Native qcap causes a new problem so can't try that as a workaround.
Native quartz needed to get this far.
The crash does not occur in Staging 2.21.
I compiled Wine 3.0-rc3 with -O0 and the crash does not occur. Compiling again
with -O1 or -O2 and the problem returns (did not try -O3). I also receive the
following warning during compilation, but further testing suggests it is not
related:
cc1: warning: unrecognized command line option ‘-Wno-packed-not-aligned’
I tried reverting 6864803f1ab70f9f9e90903b13e67da40973d12a but it did no make
any difference.
https://source.winehq.org/git/wine.git/commitdiff/6864803f1ab70f9f9e90903b1…
I also tried compiling with the following, which the man page claims GCC sets
with -O1, but the crash still didn't occur:
-fomit-frame-pointer -ftree-phiprop -ftree-sink -ftree-slsr -ftree-sra
-ftree-pta -ftree-ter -funit-at-a-time -ftree-copy-prop -ftree-copyrename
-ftree-dce -ftree-dominator-opts -ftree-dse -ftree-forwprop -ftree-fre
-fmove-loop-invariants -fshrink-wrap -fsplit-wide-types -ftree-bit-ccp
-ftree-ccp -fssa-phiopt -ftree-ch -finline-functions-called-once
-fipa-pure-const -fipa-profile -fipa-reference -fmerge-constants
-fdelayed-branch -fdse -fforward-propagate -fguess-branch-probability
-fif-conversion2 -fif-conversion -fauto-inc-dec -fbranch-count-reg
-fcombine-stack-adjustments -fcompare-elim -fcprop-registers -fdce -fdefer-pop
The crash goes away when reverting commit
01676c5dd6f9fb61b9c4e52595f6e75e21050009 and recompiling.
01676c5dd6f9fb61b9c4e52595f6e75e21050009 is the first bad commit
commit 01676c5dd6f9fb61b9c4e52595f6e75e21050009
Author: Alexandre Julliard <julliard(a)winehq.org>
Date: Sat Nov 25 11:48:02 2017 +0100
user32: Use the magic format string prefix for relay traces.
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
:040000 040000 c075dd76fd2d86e2cb8e14a300f4f8a7a8952bf4
ab6d49e1c18eae5208a19b0be062ffbf7abc8518 M dlls
Staging 2.21 does have this commit, but the binary packages do, beginning with
release 3.0-rc1.
Workaround unknown.
--
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=54272
Bug ID: 54272
Summary: ntdll-NtDevicePath breaks Wow.exe
Product: Wine-staging
Version: 8.0-rc2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: kdt3rd(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
In 8.0-rc2, the ntdll-NtDevicePath patch was updated and re-enabled. However,
this seems to cause some sort of stack corruption that causes World of Warcraft
to hard abort with a free() invalid pointer error after about 10-20 minutes.
https://bugs.winehq.org/show_bug.cgi?id=54267 has a bit more information
I added some trace calls, and 99.9% of the time it goes either into the path
where the attributes provides a root directory, or the path does not match
either \SystemRoot\ or \??\ so is processed by the original code path. However,
when it does crash, it is during processing of
\SystemRoot\system32\ntoskrnl.exe
the path is converted to
\??\C:\windows\system32\ntoskrnl.exe
and the nt_to_unix_file_name_internal function processes that correctly,
translating it to
<configroot>/c:/windows/system32/ntoskrnl.exe
but then crashes during the free of the 'name' variable at the end of (the new)
nt_to_unix_file_name. This is not the first time it did this transformation, if
I scroll back in the log, I see a few others. So something seems to be
triggering some sort of slow corruption - or debugstr_us is lying and there are
hidden non-printable characters in the above and that explains the corruption.
But I am sort of mystified, the lengths of the strings seem plausible. But if I
just remove that one patch (ntdll-NtDevicePath), all works...
--
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=54268
Bug ID: 54268
Summary: Moving the separator in regedit don't repaint listview
Product: Wine
Version: 8.0-rc2
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: wineserver
Assignee: wine-bugs(a)winehq.org
Reporter: zzhang(a)codeweavers.com
Distribution: ---
Created attachment 73833
--> https://bugs.winehq.org/attachment.cgi?id=73833
demo
Moving the separator in regedit don't repaint listview. See the attached video.
Bisect points to 33617af
33617af8145b6fadfe41d48968a728ff57b3064b is the first bad commit
commit 33617af8145b6fadfe41d48968a728ff57b3064b
Author: Jinoh Kang <jinoh.kang.kr(a)gmail.com>
Date: Mon Oct 31 22:30:20 2022 +0900
server: Don't invalidate the newly exposed child region on the parent if it
doesn't clip children.
This partly reverts e42eaaaf3a873d29b14f8f3a3617df2d0d4210ca.
Signed-off-by: Jinoh Kang <jinoh.kang.kr(a)gmail.com>
dlls/user32/tests/msg.c | 4 ----
server/window.c | 6 ++----
2 files changed, 2 insertions(+), 8 deletions(-)
--
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=54170
Bug ID: 54170
Summary: 20XX: invisible character
Product: Wine
Version: 7.19
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: regression
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: gyebro69(a)gmail.com
CC: z.figura12(a)gmail.com
Regression SHA1: 5f1cbb1b85e7d92b6c783a32ae85ca2902296481
Distribution: ArchLinux
Created attachment 73693
--> https://bugs.winehq.org/attachment.cgi?id=73693
terminal output
The character you are controlling in the game is invisible.
The buttons in the menus lack a background pattern.
This bug has appeared since
commit 5f1cbb1b85e7d92b6c783a32ae85ca2902296481
Author: Zebediah Figura <zfigura(a)codeweavers.com>
Date: Sat Jul 30 19:10:09 2022 -0500
d3d9: Use a separate draw texture for managed resources.
Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=52954
The game needs native d3dcompiler_47.dll to start.
This was tested with the Epic Games version (v1.42.13) but probably the Steam
version is also affected:
https://store.steampowered.com/app/322110/20XX/
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: NVIDIA GeForce GT 730/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 470.161.03
OpenGL core profile shading language version string: 4.60 NVIDIA
wine-8.0-rc1-75-g17e5ff74308
--
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=54023
Bug ID: 54023
Summary: d3d11:d3d11 - test_dynamic_map_synchronization() fails
on w11pro64_nv
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
d3d11:d3d11 - test_dynamic_map_synchronization() fails on w11pro64_nv:
d3d11.c:34427: Test failed: Got 0xff0000ff, expected 0xff00ff00 at (3, 5, 0),
sub-resource 0.
See https://test.winehq.org/data/patterns.html#d3d11:d3d11
Note: w11pro64_nv is the TestBot's NVIDIA RTX3050 PCI passthrough Windows 11
21H2 VM. The plain QXL (QEmu), and AMD PCI passthrough test configurations have
d3d11:d3d11 failures too but in other test functions.
--
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=53995
Bug ID: 53995
Summary: d2d1:d2d1 runs out of GL memory and crashes on the
debian 11 VM
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: d2d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
d2d1:d2d1 runs out of GL memory and crashes on the debian 11 VM:
d2d1.c:7145: Test marked todo: Figure does not match.
Unhandled exception: page fault on write access to 0x00000000 in 32-bit code
(0x6ab30fe4).
[...]
Backtrace:
=>0 0x6ab30fe4 memset+0x24(dst=0x000000000, c=0, n=0x12c000)
[Z:\home\winetest\tools\testbot\var\wine\dlls\msvcrt\string.c:3205] in ucrtbase
(0x0685f908)
1 0x008a9073 wined3d_texture_load_location+0x423(texture=002CB990,
sub_resource_idx=0, context=00289F90, location=0x8)
[Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\texture.c:862] in wined3d
(0x0685f9a8)
2 0x00897fce surface_cpu_blt+0x9ee(dst_texture=002CB990,
dst_sub_resource_idx=0, dst_box=0685FB38, src_texture=0028D170,
src_sub_resource_idx=0, src_box=0685FB50, flags=0x20000000, fx=0685FB68,
filter=WINED3D_TEXF_POINT)
[Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\surface.c:752] in wined3d
(0x0685faf8)
3 0x00899ac2 cpu_blitter_blit+0xc2(blitter=002BB820,
op=WINED3D_BLIT_OP_RAW_BLIT, context=00289F90, src_texture=0028D170,
src_sub_resource_idx=0, src_location=0x10, src_rect=0685FE10,
dst_texture=002CB990, dst_sub_resource_idx=<is not available>,
dst_location=0x8, dst_rect=0685FE20, color_key=00000000,
filter=WINED3D_TEXF_POINT, resolve_format=00000000)
[Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\surface.c:1328] in
wined3d (0x0685fb98)
4 0x008b7622 ffp_blitter_blit+0xa2(blitter=002BB838,
op=WINED3D_BLIT_OP_RAW_BLIT, context=00289F90, src_texture=0028D170,
src_sub_resource_idx=0, src_location=0x10, src_rect=0685FE10,
dst_texture=002CB990, dst_sub_resource_idx=0, dst_location=0x8,
dst_rect=0685FE20, colour_key=00000000, filter=WINED3D_TEXF_POINT,
resolve_format=00000000)
[Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\texture.c:6190] in
wined3d (0x0685fc58)
5 0x0085d36d glsl_blitter_blit+0x1ad(blitter=002BB850,
op=WINED3D_BLIT_OP_RAW_BLIT, context=00289F90, src_texture=0028D170,
src_sub_resource_idx=0, src_location=0x10, src_rect=0685FE10,
dst_texture=002CB990, dst_sub_resource_idx=0, dst_location=0x8,
dst_rect=0685FE20, colour_key=00000000, filter=WINED3D_TEXF_POINT,
resolve_format=00000000)
[Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\glsl_shader.c:13270] in
wined3d (0x0685fd78)
6 0x0089ada1 texture2d_blt+0x3c1(dst_texture=002CB990,
dst_sub_resource_idx=0, dst_box=05B678B4, src_texture=0028D170,
src_sub_resource_idx=0, src_box=05B678D4, flags=0x20000000, fx=05B678F0,
filter=WINED3D_TEXF_POINT)
[Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\surface.c:1639] in
wined3d (0x0685fe48)
7 0x0081b8ad wined3d_cs_exec_blt_sub_resource+0xcd(cs=05B50020,
data=05B678A8) [Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\cs.c:2579]
in wined3d (0x0685fec8)
8 0x0081d37b wined3d_cs_command_unlock(queue=<internal error>, cs=<internal
error>) [Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\cs.c:3310] in
wined3d (0x0685ff28)
9 0x0081d37b wined3d_cs_execute_next+0x53(ctx=<couldn't compute location>)
[Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\cs.c:3309] in wined3d
(0x0685ff28)
10 0x0081d37b wined3d_cs_run+0x13b(ctx=<couldn't compute location>)
[Z:\home\winetest\tools\testbot\var\wine\dlls\wined3d\cs.c:3376] in wined3d
(0x0685ff28)
[...]
7145 is the most common last trace seen, though 7033 also appears at least
once, but running with WINETEST_REPORT_SUCCESS I get different locations.
See https://test.winehq.org/data/patterns.html#d2d1:d2d1
Furthermore when reproducing this I saw out-of-memory traces right before the
crash. For instance:
d2d1.c:601: Test succeeded
01d8:err:d3d:wined3d_debug_callback 00291C38: "GL_OUT_OF_MEMORY in
glBufferStorage".
01d8:err:d3d:wined3d_debug_callback 00291C38: "GL_INVALID_VALUE in
glMapBufferRange(offset 0 + length 67108864 > buffer_size 0)".
01d8:err:d3d:wined3d_allocator_chunk_gl_map Failed to map chunk memory.
01d8:err:d3d:wined3d_bo_gl_map Failed to map chunk.
01d8:err:d3d:wined3d_context_gl_map_bo_address Failed to map bo.
wine: Unhandled page fault on write access to 00000000 at address 6AB30FE4
(thread 01d8), starting debugger...
It's not clear why only the debian11 VM is impacted: it has a dual-screen
configuration but so does debiant so it does not appear to be a multi-monitor
thing, and this does not happen on fgtb-debian11 or debian11b so it's not a
Debian version issue.
--
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=53752
Bug ID: 53752
Summary: Rayman 3: glitched graphics (black textures)
Product: Wine
Version: 7.3
Hardware: x86-64
URL: https://archive.org/download/rayman-3-pc-demo/Rayman3_
PC-Demo.zip
OS: Linux
Status: NEW
Keywords: download, regression
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: gyebro69(a)gmail.com
CC: z.figura12(a)gmail.com
Regression SHA1: 1b1b03055db8bf03c6783d4fcb19abf670d53338
Distribution: ---
There are lots of black textures in Rayman 3 thus not so much of the game can
be seen.
Can be reproduced with the demo: the issue is already present in the main menu.
According to my testing the problem appeared with
commit 1b1b03055db8bf03c6783d4fcb19abf670d53338
wined3d: Try to allocate new OpenGL BOs from the client thread for DISCARD
maps.
With the previous commit in-game scenery looks good.
Workaround: disable hardware TnL in the video settings utility called
R3_Setup_DX8.exe in the demo.
Rayman3_PC-Demo.zip (184M)
md5: d6d3c2d76931feff73f56295a0dee6a3
Still present in wine-7.18-120-g001665d7354.
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: NVIDIA GeForce GT 730/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 470.141.03
OpenGL core profile shading language version string: 4.60 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=53640
Bug ID: 53640
Summary: Bully: Scholarship Edition hangs on loading screen and
doesn't play intros
Product: Wine
Version: 7.15
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: regression
Severity: normal
Priority: P2
Component: quartz
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
CC: rbernon(a)codeweavers.com
Regression SHA1: 4608e1e1257a377cd554a0e885368e3feb7d286f
Distribution: ---
Loading screen is shown until mouse is clicked then you're getting to main
menu.
It's back to normal after deleting the registry path.
--
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=47828
Bug ID: 47828
Summary: regedit: Random crashes on selecting an entry
(thread-related?)
Product: Wine
Version: 4.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ed7-aspire4925(a)hotmail.com
Distribution: ---
Created attachment 65333
--> https://bugs.winehq.org/attachment.cgi?id=65333
commented logs from the various crashes
As described above. By selection I meant double-clicking or pressing [return]
on a highlighted entry
Sometimes the "debuggee" works, sometimes it doesn't.
Sometimes the back trace shows, sometimes it doesn't.
Sometimes the application crash window doesn't even appear.
Definitely a threading issue...
The crash occurs at around the eighth key selection.
--
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=48322
Bug ID: 48322
Summary: World of Warcraft Classic: Mouse movement can block
keydown events from registering
Product: Wine-staging
Version: 5.0-rc1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: m.schaefer8(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
This seems to be a regression:
I've noticed this in the game World of Warcraft Classic. In Wine 4.17.r11
mouse/keyboard behave as expected. With 5.0-rc1 when keeping the right mouse
button clicked *and* moving the mouse (changing character orientation and view
orientation with the mouse) all other keydown events are ignored. Moving the
mouse by itself does not block keydown events; keeping the button pressed but
not moving the mouse also does not block keydown events.
Keyup events are processed as normal.
Software I'm using is specifically Wine-Staging with TKG patches.
Having never filed bugs for Wine before, please inform me if you require
additional information, logs (and how to acquire said logs), etc.
--
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.