https://bugs.winehq.org/show_bug.cgi?id=55060
Bug ID: 55060
Summary: d3d9:d3d9ex - test_wndproc() is sometimes missing a
WM_SIZE message in Wine (GitLab CI)
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
d3d9:d3d9ex - test_wndproc() is sometimes missing a WM_SIZE message in Wine:
d3d9ex.c:3179: Test failed: Expected message 0x5 for window 0, but didn't
receive it, i=0.
d3d9ex.c:3199: Test failed: Expected message 0x5 for window 0, but didn't
receive it, i=0.
d3d9ex.c:3205: Test failed: Got unexpected WINDOWPOS hwnd=00000000, x=0, y=0,
cx=0, cy=0, flags=0
See https://test.winehq.org/data/patterns.html#d3d9:d3d9ex
This has started happening almost systematically in the GitLab CI's Debian
environment on 2023-06-07.
However this is not the first time these failures happen in Wine.
* They happened about 50 times on gitlab-debian-* between 2022-10-14 and
2023-01-13.
* During the same period there has been some sporadic instances on debian11b:
- 2022-11-01 debian11b-wow32
- 2022-11-07 debian11-win32-he-IL
- 2022-11-11 debian11b-wow64
- 2022-11-14 debian11-win32-fr-FR
* 2023-02-09 gitlab-debian-64
* And then nothing for the TestBot and GitLab CI VMs until this new
GitLab-specific rash on 2023-06-07.
It should be noted that they happen pretty often on Remi's test environments,
though it's limited to rbernon-x11-fvwm since 2023-06-02.
So the issue is likely that some other test is messing up the environment and
causing these failures.
--
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=53877
Bug ID: 53877
Summary: vbscript compile_assignment assertion when assigning
multidimensional array by indices
Product: Wine
Version: 7.20
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: vbscript
Assignee: wine-bugs(a)winehq.org
Reporter: jsm174(a)gmail.com
Distribution: ---
The following works in real vbscript:
Dim x
Redim x(10)
x(1) = Array(5, 6, 7)
WScript.echo x(1)(0)
WScript.echo x(1)(2)
x(1)(0) = x(1)(2)
WScript.echo x(1)(0)
Output:
5
7
7
When running through Wine vbscript an assertion happens when processing
x(1)(0) = x(1)(2)
case EXPR_CALL:
call_expr = (call_expression_t*)left;
assert(call_expr->call_expr->type == EXPR_MEMBER);
Stepping through the debugger, call_expr->call_expr->type appears to be
EXPR_CALL
--
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=50859
Bug ID: 50859
Summary: X Error of failed request: GLXBadFBConfig
Product: Wine-staging
Version: 6.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: linsilstef(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
[stefan@yuntani Downloads]$ wine64 Gw2Setup-64.exe
0034:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1.
005c:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1
0064:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1
006c:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1
002c:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1
0024:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1
00f4:fixme:font:get_name_record_codepage encoding 20 not handled, platform 1
0024:fixme:heap:RtlSetHeapInformation 0000000000020000 0 000000000022FD30 4
0024:fixme:heap:RtlSetHeapInformation 0000000001620000 0 000000000022FD10 4
0024:fixme:heap:RtlSetHeapInformation 0000000001620000 1 0000000000000000 0
0024:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFO
X Error of failed request: GLXBadFBConfig
Major opcode of failed request: 150 (GLX)
Minor opcode of failed request: 0 ()
Serial number of failed request: 218
Current serial number in output stream: 218
The error also occurs in wine 6.3. and Wine 6.4
System Fedora 34 Mesa version 21.0.0-2
--
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=43708
Bug ID: 43708
Summary: Major terrain glitching on SPORE
Product: Wine-staging
Version: 2.14
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: emily.shadowsong(a)gmail.com
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
Created attachment 59176
--> https://bugs.winehq.org/attachment.cgi?id=59176
Clearly, it's already getting wierd...
I've been playing SPORE for a while now, it has worked normally; at one point
in playing I pressed ALT+TAB and the whole terrain just glitched. It shows up
that way on the map, it's not graphics-related because I can physically touch
the messed-up land. There's sometimes jagged spikes, often times lines through
the planet, and extremely tall mountains, making the game practically
unplayable unless I have wings. Sometimes it'll appear as though my nest
spawned inside water, and if I try to walk out of the water and onto what looks
like land I'll be eaten by the fish monster. I've reinstalled SPORE about five
times now and it hasn't helped. I've tried running SPORE on safe mode as well.
I have the core SPORE, galactic adventures, and creepy & cute parts pack.
Every time I alt tab, the terrain changes again and gets more and more messed
up.
--
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=55048
Bug ID: 55048
Summary: Bandai Namco Launcher Starter fails installation with
Out Of Range error
Product: Wine
Version: 8.10
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: funtimeschaos(a)rocketmail.com
Distribution: ---
The program in question can be downloaded here:
https://object-bnolauncher-pf.bandainamco-ol.jp/launcher/BandaiNamcoLaunche…
It starts fine for me, although with some visual glitches. I uncheck all the
boxes (create shortcuts, restart etc) and press the big orange "install"
button.
It starts installing, but then shows the following error dialog and crashes:
"Runtime error (at 13:589): Out Of Range."
--
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=55021
Bug ID: 55021
Summary: The Evil Within shows a black screen with OpenGL
renderer
Product: Wine
Version: 8.9
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: winex11.drv
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
CC: pgofman(a)codeweavers.com
Distribution: ---
Before commit 446da60e78beb321d776b48cdee6f764c81b924b the game worked as a
slide show. Now the performance feels normal, but it brings a black screen with
sound.
So it's just changing from one bad state to another.
--
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=49588
Bug ID: 49588
Summary: Cannot build wine with GCC 10 and Address Sanitizer
Product: Wine
Version: 5.13
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mikrutrafal(a)protonmail.com
Distribution: ---
Created attachment 67745
--> https://bugs.winehq.org/attachment.cgi?id=67745
config.log
Hi,
When I tried to compile Wine with address sanitizer with GCC 10 with this
command
```
./configure --enable-win64 CFLAGS="-Og -fsanitize=address"
LDFLAGS="-fsanitize=address -lasan -lpthread"
make -j8
```
then this errors prints to config.log when configuring build
```
configure:4663: gcc -V >&5
gcc: error: unrecognized command-line option '-V'
gcc: fatal error: no input files
compilation terminated.
configure:4663: gcc -qversion >&5
gcc: error: unrecognized command-line option '-qversion'; did you mean
'--version'?
gcc: fatal error: no input files
compilation terminated.
```
--
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=47193
Bug ID: 47193
Summary: Sony Vegas PRO 16 reports successful installation but
there are no files installed
Product: Wine-staging
Version: 4.8
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: donanykey(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 64442
--> https://bugs.winehq.org/attachment.cgi?id=64442
WINEDEBUG=+msi
Hi
Vegas PRO 16 trial installer reports successful installation but there are no
files actually installed.
P.s. All installation options unchecked other than Vegas PRO itself
Best
D
--
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=55037
Bug ID: 55037
Summary: vbscript: Colon on new line after if fails
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: vbscript
Assignee: wine-bugs(a)winehq.org
Reporter: francisdb(a)gmail.com
Distribution: ---
looks similar to bug 54234 but then for the Then instead of the Else
```
If Keycode = StartGameKey Then
:pupevent 800
End If
```
without the colon this works
```
If Keycode = StartGameKey Then
pupevent 800
End If
```
--
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=54988
Bug ID: 54988
Summary: Final Fantasy XIV: Japanese IME behavior incorrect
Product: Wine
Version: 8.9
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winex11.drv
Assignee: wine-bugs(a)winehq.org
Reporter: achurch+wine(a)achurch.org
Regression SHA1: d9fc3eab9a4ae39c94fa484d65679de22d02e75a
Distribution: ---
Final Fantasy XIV: Japanese IME behavior incorrect
As of Wine 8.8, when using a Japanese input method editor (IME), the IME
is no longer disabled in cases where it should be, such as the following:
1) Log in to Final Fantasy XIV (get in-game).
2) Click on the chat input bar to enter text entry mode.
3) Enable the Japanese IME (so that Japanese text can be typed).
4) With the IME active, press Enter to leave text entry mode.
Expected behavior: The IME is disabled, so that keyboard controls (WASD
etc.) are properly recognized.
Observed behavior: The IME remains enabled, preventing keyboard controls
from working until the user disables the IME manually.
This is a regression from Wine 8.7; git bisect identifies
d9fc3eab9a4ae39c94fa484d65679de22d02e75a as introducing the regression.
--
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.