https://bugs.winehq.org/show_bug.cgi?id=54542
Bug ID: 54542
Summary: d3dx10_38:d3dx10, d3dx10_40:d3dx10, d3dx10_41:d3dx10,
d3dx10_42:d3dx10 & d3dx10_43:d3dx10 regularly get
D3DXERR_INVALIDDATA
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: d3d-util
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
d3dx10_38:d3dx10, d3dx10_40:d3dx10, d3dx10_41:d3dx10, d3dx10_42:d3dx10 &
d3dx10_43:d3dx10 regularly get unexpected hr values in test_get_image_info()
and test_create_texture().
For instance on 2023-02-15 on w1064 the 32-bit d3dx10_43:d3dx10 test got:
d3dx10.c:2677: Test failed: Test 0: Got unexpected hr2 0xdeadbeef.
d3dx10.c:2686: Test failed: Test 0: Got unexpected hr2 0xdeadbeef.
d3dx10.c:2677: Test failed: Test 2: Got unexpected hr2 0xdeadbeef.
d3dx10.c:2686: Test failed: Test 2: Got unexpected hr2 0xdeadbeef.
d3dx10.c:2868: Test failed: Test 0: Got unexpected hr 0x88760b59.
d3dx10.c:2870: Test failed: Test 0: Got unexpected hr2 0xdeadbeef.
d3dx10.c:2881: Test failed: Test 0: Got unexpected hr 0x88760b59.
d3dx10.c:2883: Test failed: Test 0: Got unexpected hr2 0xdeadbeef.
d3dx10.c:2868: Test failed: Test 2: Got unexpected hr 0x88760b59.
d3dx10.c:2870: Test failed: Test 2: Got unexpected hr2 0xdeadbeef.
d3dx10.c:2881: Test failed: Test 2: Got unexpected hr 0x88760b59.
d3dx10.c:2883: Test failed: Test 2: Got unexpected hr2 0xdeadbeef.
See https://test.winehq.org/data/patterns.html#d3dx10_34:d3dx10
Where 0x88760b59 == D3DXERR_INVALIDDATA
This is similar to the d3dx10_34:d3dx10 issue bug 54541 but there are key
differences:
* In bug 54541 it is always the same two checks that fail, whereas here it's a
different set of failures with every run, with anywhere from 4 to 78 failures.
* Bug 54541 never had failures in test_create_texture().
* Also this bug's failures seem to have started some time around 2023-01-07,
i.e. much more recently than the ones in bug 54541.
--
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=52661
Bug ID: 52661
Summary: The Life and Suffering of Sir Brante Crashes Often
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: matthewcboyd(a)tutanota.com
Distribution: ---
Created attachment 71983
--> https://bugs.winehq.org/attachment.cgi?id=71983
Log File
I am trying to play The Life and Suffering of Sir Brante from GOG using Wine.
It crashes at different times always with the same error in the log file. Now
here's what's really interesting: it doesn't do this on the demo. I can
actually boot up the demo, get past where it crashes on the full version, copy
my save into the full game and keep going. Problem is it will crash again down
the road and I am more than convinced this will happen past where the demo
ends. The crashes are always at specific points and are reproducable.
The part of the log file that I think is interesting is this:
"ERROR: Caught a segmentation fault while loading plugin file:
/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so"
The file is installed properly and this happens on Manjaro as well as Mint.
My System:
AMD Ryzen 5 2600X | 16GB DDR4-3000 CL15 | MSI RX 580 8GB Gaming X | Mesa 21.2.6
| Linux Mint 20.3 | Mate 1.26.0 | Kernel 5.4.0-104-generic
--
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=45613
Bug ID: 45613
Summary: Total War: Arena crashes with enabled d3dcompiler_47
Product: Wine
Version: 3.13
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: dark.shadow4(a)web.de
Depends on: 45593, 45599, 45602, 45603
Distribution: ---
Make sure you work around the dependent bugs.
The game starts up, but then crashes with a blackscreen.
Suspicious log from +relay
> 009d:Call d3dcompiler_47.D3DReflect(030e20d0,00000350,56913238,0033dac0) ret=55f79bfd
> 009d:Ret d3dcompiler_47.D3DReflect() retval=80004002 ret=55f79bfd
> 009d:Call KERNEL32.OutputDebugStringW(030e1ef0 L"d3d call failed (0x80004002) : unspecified\n") ret=55134092
> 009d:Ret KERNEL32.OutputDebugStringW() retval=00000000 ret=55134092
Disabling d3dcompiler_47 works around the issue (for some reason).
Note:
To easier debug this issue, go to drive_c/users/USERNAME/Application Data/The
Creative Assembly/Arena/scripts/preferences.script.txt and set gfx_fullscreen
to false.
--
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=41225
Bug ID: 41225
Summary: League of Legends: Login Status randomly
fails/succeeds
Product: Wine
Version: 1.9.17
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: nmschulte(a)gmail.com
Distribution: ---
Created attachment 55493
--> https://bugs.winehq.org/attachment.cgi?id=55493
stderr + stdout
amd64 Debian Sid, multi-arch (Intel Haswell)
wine-development version wine-1.9.17 (Debian 1.9.17-1)
wine-stable version wine-1.8.3 (Debian 1.8.3-3)
When logging in to the game, sometimes the login works immediately (rare),
sometimes the login seems to timeout multiple times in a row and fails after 3
re-attempts, and sometimes it succeeds after a few re-attempts.
I have attached a log where my first "login" failed after three request
attempts; I then pressed the button again (second "login"), which was
re-attempted twice but succeeded after the second re-attempt.
Please see the screenshots for reference.
After having dealt with this issue for a while (since I've ever been playing
League of Legends on Wine, which was v1.5 or v1.6; definitely same issue w/
v1.7), I've noticed a few quirks:
I have a hunch this has to do w/ SSL/TLS (HTTPS) or part of the certificate
chain.
It seems that having iexplore.exe open in the background/prior makes the login
more likely to succeed. Just a feeling, not 100% certain this helps.
If I enter a bad password, the responses seem to _always_ come back right away
(or very, very quickly). I have had decent success "working around" this issue
by:
1) copying my correct password to the clipboard (usually by CTRL+X'ing it after
typing it in the username field)
2) issuing a rapid succession of "logins" with incorrect passwords, until the
(login failed) response comes back _very quickly_, usually after 3 or 4
"logins"
3) quickly pasting my correct password and logging in
Usually, this signs me in on the very first "login" request/response (no
"attempt #" re-attempts).
--
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=34512
Bug #: 34512
Summary: DDO client Freeze up
Product: Wine
Version: 1.7.1
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: Linuxhelper2881(a)yahoo.com
Classification: Unclassified
Created attachment 45941
--> http://bugs.winehq.org/attachment.cgi?id=45941
DDO wine1.7.1. output
when u start the Client it Freezes up while it try's to load the Downloading
"EN-Splash-screen". log and output is here need any thing else just ask
--
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=18443
Summary: Could not initiate GoogleTalkPlugin connection in Google
Video/Voice chat
Product: Wine
Version: 1.1.21
Platform: PC
URL: http://www.gmail.com/
OS/Version: Linux
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: winsock
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: thestig(a)google.com
Created an attachment (id=21044)
--> (http://bugs.winehq.org/attachment.cgi?id=21044)
+ws2_32,+winsock log
To reproduce:
1. Install win32 Firefox 3.0.x.
2. Login to Gmail.
3. Attempt to try the video/voice chat, download the plugin. (downloading
http://dl.google.com/googletalk/googletalkplugin/GoogleVoiceAndVideoSetup.e…
directly does not work)
4. Close win32 Firefox.
5a. run winetricks msxml3
5b. install GoogleVoiceAndVideoSetup.exe (It will say error 0x80040509 even
though it installed - bug 18442)
6. Move the content of c:\Program Files\'Mozilla Firefox' into the appropriate
place under c:\Program Files\Mozilla Firefox. (bug 18441)
7. Start win32 Firefox.
8. Login to Gmail.
Once the chat window loads, you should get the following on the console:
trace:winsock:WSACreateEvent
trace:winsock:WSAStartup verReq=1
trace:winsock:WSAStartup succeeded
err:ntdll:NtQueryInformationToken Unhandled Token Information class 25!
[000:002] Could not initiate GoogleTalkPlugin connection
--
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=54766
Gijs Vermeulen <gijsvrm(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |CLOSED
--- Comment #2 from Gijs Vermeulen <gijsvrm(a)gmail.com> ---
Closing.
--
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=54967
Bug ID: 54967
Summary: Star Citizen launcher fails to start with javascript
error
Product: Wine
Version: 8.7
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: o.dierick(a)piezo-forte.be
Distribution: ---
Created attachment 74494
--> https://bugs.winehq.org/attachment.cgi?id=74494
Screenshot of the JavaScript error dialog from starting the Star Citizen
launcher
Hello,
Star Citizen is free for a limited time.
Last time I tried it was in November '22. I could start the launcher (1.6.1)
and game client and the only issue I had was the low performance (reported as
bug 54010).
The launcher is now a new version (1.6.6) and I'm unable to start it. It
displays an error message from JavaScript and nothing happens when dismissed. I
have to kill the residual process (CrBrowserMain - presumably a libcef/webkit
helper).
Regards.
--
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=54244
Bug ID: 54244
Summary: cardfile windows are grayed out
Product: Wine-staging
Version: 8.0-rc2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mmikeinsantarosa(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 73797
--> https://bugs.winehq.org/attachment.cgi?id=73797
grayed out window example
All cardfile.exe windows are grayed out.
Here is a link to my goolge drive for cardfile.exe for testing
https://drive.google.com/file/d/1uIJo1qtE1sQYQvgUsjiYHxBbU-ZhXehk/view?usp=…
This bug has been present since wine-staging-6.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=53961
Bug ID: 53961
Summary: Saints Row 2022 doesn't start
Product: Wine
Version: 7.21
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 off from bug 53954. For wine-7.21, you need the patch from this bug.
When starting the game, there is a SaintsRow.exe process, but the game doesn't
start.
--
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.