https://bugs.winehq.org/show_bug.cgi?id=51976
Bug ID: 51976
Summary: The Elder Scrolls Online crashes at startup since it
auto-updated to v7.2.5 on Nov 1 2021
Product: Wine
Version: 6.17
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 70965
--> https://bugs.winehq.org/attachment.cgi?id=70965
default terminal output (wine 6.20)
Hello,
After upgrading the game The Elder Scrolls Online to v7.2.5 (Deadlands & Update
32) on Nov 1, I can no longer start the application.
I was using Wine 6.17 at the time (had no issue with it before the game update)
and upgraded to 6.19, then 6.20, and got the same result.
The launcher works fine, but as soon as I click the PLAY button, a wine debug
dialog pops-up about a crash in the game client (eso64.exe - this is a 64bit
app).
The patch notes of the game speaks of changes in Nvidia DLSS & DLAA and
Multithreaded Rendering, but a +relay log shows that the crash occurs right
after a call to BluetoothFindFirstRadio(), in the same thread. I don't recall
seeing that function before so that may be an unmentioned change to the
application, or it may have nothing to do with the crash; I don't know (yet).
https://forums.elderscrollsonline.com/en/discussion/590109/pc-mac-patch-not…
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=49515
Bug ID: 49515
Summary: Star Wars: The Old Republic unable to patch on Debian
but works on Mint
Product: Wine
Version: 5.12
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: toad(a)amphibian.dyndns.org
Distribution: ---
Created attachment 67644
--> https://bugs.winehq.org/attachment.cgi?id=67644
Wine log of running the launcher
The SWTOR launcher is unable to patch itself, or to patch the game, and hence
refuses to start the game even if it is actually up to date. However, it works
on Linux Mint 19.3 (with the Xenial packages; the recommended bionic packages
do not install).
Debug output from Wine is not obviously helpful. Logs from SWTOR show an
UnzipFailed error which is suspicious. Wine logs show nothing obviously
helpful.
I am using all the usual precautions for SWTOR:
- Run the original installer in wine-devel. The installer does not work with
staging. However, the patcher has the same issues on both.
- On an affected system, the launcher hangs trying to patch itself, with errors
in the SWTOR log. This can be fixed using the launcher repair utility. On Mint,
it shows a bunch of assertion error dialogs, and works.
- Login and accept the EULA, at this point it will complain about BitRaider.
Exit and modify launcher.settings as usual to turn off BitRaider.
- At this point, on Mint, Wine 5.11 is downloading the game successfully. On
any version of Debian, it shows the error "Unable to retrieve patch data.
Please check network connection. (206)". The TOR log shows the unzip error. I
think the unzip error and the problems with the patcher patching itself are
probably the same bug.
This stopped working around the time of Wine 5.10, I think because of an update
to the launcher. It does not work on Debian 9, 10 or 11 on staging 5.11. On
Debian 11, it does not work on staging 5.11 or devel 5.12.
--
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=50227
Bug ID: 50227
Summary: Logos 8 indexer crashes
Product: Wine
Version: 5.20
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: galanlama(a)gmail.com
Distribution: ---
Created attachment 68735
--> https://bugs.winehq.org/attachment.cgi?id=68735
Backtrace produced by the wine debugger.
After opening Logos, indexer crashes after a few seconds. Same result by
running indexer.exe directly.
--
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=15505
Summary: STM_SETIMAGE does not handle bitmaps with alpha
correctly
Product: Wine
Version: 1.1.5
Platform: PC
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P2
Component: user32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: thestig(a)google.com
In XP, STM_SETIMAGE makes a copy of bitmaps with alpha, which allows
applications to delete the bitmaps they passed in. Many programmers expect this
as the default behavior, since they don't test on older Windows platforms.
Our STM_SETIMAGE implementation still follows the pre-XP behavior, which may
cause rendering problems for apps that use STM_SETIMAGE extensively.
I don't have a minimal test case just yet...
--
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=52919
Bug ID: 52919
Summary: Resident Evil 5 DVD shows
E_INVALIDARG:XLiveInitialize(&xii)
Product: Wine
Version: 7.7
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: BOBBLOG(a)protonmail.com
Distribution: ---
Created attachment 72299
--> https://bugs.winehq.org/attachment.cgi?id=72299
RE5-D3D
Resident Evil 5 DVD shows E_INVALIDARG:XLiveInitialize(&xii) when i launch the
game.
This was tested with wine-7.7 in a clean wine prefix. I'll attach +d3d log.
--
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=43347
Bug ID: 43347
Summary: valgrind shows an unintialized read in
dlls/iphlpapi/tests/iphlpapi.c
Product: Wine
Version: 2.12
Hardware: x86
OS: Linux
Status: NEW
Keywords: download, source, testcase, valgrind
Severity: normal
Priority: P2
Component: iphlpapi
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
Distribution: Gentoo
../../../tools/runtest -q -P wine -T ../../.. -M iphlpapi.dll -p
iphlpapi_test.exe.so iphlpapi && touch iphlpapi.ok
==10952== Syscall param ioctl(SIOCGIFINDEX) points to uninitialised byte(s)
==10952== at 0x4338F79: ioctl (syscall-template.S:84)
==10952== by 0x435916D: if_nametoindex (if_index.c:47)
==10952== by 0x4B25E43: getInterfaceIndexByName (ifenum.c:143)
==10952== by 0x4B2EC7E: IPHLP_if_nametoindex (iphlpapi_main.c:3233)
==10952== by 0x488198E: test_interface_identifier_conversion
(iphlpapi.c:1958)
==10952== by 0x48831AB: func_iphlpapi (iphlpapi.c:2230)
==10952== by 0x4884014: run_test (test.h:603)
==10952== by 0x4884465: main (test.h:687)
==10952== Address 0x4b0f8c0 is on thread 1's stack
==10952== in frame #1, created by if_nametoindex (if_index.c:35)
==10952== Uninitialised value was created by a stack allocation
==10952== at 0x4359141: if_nametoindex (if_index.c:41)
==10952==
--
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=44337
Bug ID: 44337
Summary: d3d9/tests/device.ok fails on Nvidia (Nouveau drivers)
in test_occlusion_query()
Product: Wine
Version: 3.0-rc5
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: z.figura12(a)gmail.com
Distribution: ---
with the following lines:
device.c:5915: Test failed: Got unexpected hr 0x1.
device.c:5919: Test failed: Got unexpected hr 0x1.
device.c:5920: Test failed: Got unexpected query result 0xffffffffffffffff.
It would be nice to fix this as this is currently the only D3D test failure on
the cw2 test machine.
--
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=48820
Bug ID: 48820
Summary: user32:win "unexpected 0x7fff message" Japanese
Windows 10 failures
Product: Wine
Version: unspecified
Hardware: x86
OS: Windows
Status: NEW
Severity: major
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
The TestBot's w1064v1809-zh_CN configuration runs the tests on Windows 10 1809
in a Chinese locale. This test configuration gets unique failures in
user32:win:
win.c:3852: Test failed: hwnd 007404D2 message 7fff
win.c:3858: Test failed: message 7fff available
win.c:3931: Test failed: hwnd 007404D2/0054050A message 7fff
win.c:3934: Test failed: hwnd 007404D2/0054050A message 7fff
Note how these messages are very similar to the IME messages in bug 48819.
However 0x7fff is a totally unknown message: all I can say about it is that
it's WM_APP-1. So maybe it's another IME system. Maybe not?
See: https://test.winehq.org/data/tests/user32:win.html
However note that quite often WineTest fails to submit its results to
test.winehq.org, typically because it times out. So you can more easily find
the latest failure by looking for the "32 bit WineTest: base VMs" jobs on the
TestBot.
Finally, three of these messages include the window handles which means they
are "always new". Because of this the TestBot will mistakenly attribute the
failure to any user32 patch submitted to wine-devel, which should cause them to
be rejected. So I bumped the priority on this bug.
--
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=35765
Bug ID: 35765
Summary: gdi32:font / richedit:editor / msvcrt:locale /
msvcrt:string fails on newtb-w7u
Product: Wine
Version: 1.7.14
Hardware: x86
OS: Linux
Status: NEW
Keywords: source, testcase
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fracting(a)gmail.com
CC: fgouget(a)codeweavers.com
http://test.winehq.org/data/770213e16c6918728f69ea33545fafabd59dbc8e/win7_n…
It seems these tests are all related to locales, and they fail much more on
this machine than other machine.
SystemDefaultLCID 411
UserDefaultLCID 409
ThreadLocale 411
UserDefaultUILanguage 411
ThreadUILanguage 411
It doesn't happen frequently that we have a vm with different UserDefaultLCID
and SystemDefaultLCID. I'm not very sure if we want to support such a case, it
maybe useful in real world for some body. (I personally don't care too much
lol)
François, is there any chance to try:
1. set all LCIDs to 0x409 (Simplified Chinese)
2. set all LCIDs to 0x411 (Japanese)
Then reboot the vm, then resubmit the tests, to see if there is any
improvement?
Thanks for your great work! Everyone wants your patch/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.