July 2021 - Wine-bugs - list.winehq.org

[Bug 33807] New: Objects disappear at certain camera angles in Ground Control
by wine-bugs＠winehq.org 13 Feb '23

13 Feb '23

http://bugs.winehq.org/show_bug.cgi?id=33807 Bug #: 33807 Summary: Objects disappear at certain camera angles in Ground Control Product: Wine Version: 1.6-rc2 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: tdsbug(a)gmail.com Classification: Unclassified Created attachment 44813 --> http://bugs.winehq.org/attachment.cgi?id=44813 Terminal output without WINEDEBUG Game: Ground Control, version 1.0.0.5, crack for version 1.0.0.7 (versions have no effect on this issue) ***Problem***: Some objects become invisible at random times. When this happens, shadows still work properly. Often only certain parts of an object become invisible, like only chassis of tank. This doesn't happen with visual effects, like lights and fire. Camera angle has some limited effect on the moment when this happens. I am running the game in hardware rendering mode. (Game also has software rendering mode, but only for 640x480 resolution. Some similar glitches appear in software mode too) According to appdb, this has been happening forever and is not a regression. The game uses directx 7. Logs attached. ***Additional details***: During installation, the game asked to install directx 7.0a, which I clicked no. Also tried clicking yes, but it has no effect. No dll overrides, winetricks or anything was used. The game also suffers from input slowdown at certain times, but it's probably a different bug. Also, this game is a free download now, so you can try yourself if you wish. -- 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.

2 14

[Bug 50469] New: The Void crashes with builtin d3dx9_36 (needs D3DXDisassembleShader implementation)
by WineHQ Bugzilla 12 Feb '23

12 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=50469 Bug ID: 50469 Summary: The Void crashes with builtin d3dx9_36 (needs D3DXDisassembleShader implementation) Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d-util Assignee: wine-bugs(a)winehq.org Reporter: titan.costa(a)gmail.com Distribution: --- The game version is from GOG. After making D3DXFillCubeTextureTX() return S_OK (bug #48528), the game crashes after D3DXDisassembleShader call as it does not check the returned value. -- 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.

1 5

[Bug 38905] New: In dlls/mshtml/tests, "make test" failed when some Chinese fonts are used
by wine-bugs＠winehq.org 08 Feb '23

08 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=38905 Bug ID: 38905 Summary: In dlls/mshtml/tests, "make test" failed when some Chinese fonts are used Product: Wine Version: 1.7.47 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: litimetal(a)gmail.com Distribution: --- Created attachment 51840 --> https://bugs.winehq.org/attachment.cgi?id=51840 backtrace.txt 0. Copy some Chinese fonts from C:\windows\fonts in Windows XP to ~/.fonts[1] 1. fc-cache -fv 2. run "make test" in dlls/mshtml/tests 3. crashed [1]: The fonts I copied to Linux: 文鼎CS长宋体繁.TTF 文鼎粗行楷简.TTF 文鼎粗圆简.TTF 文鼎琥珀繁.TTF 文鼎特粗宋简.TTF 文鼎小标宋简.TTF 文鼎报宋简.TTF 文鼎粗黑繁.TTF 文鼎大标宋简.TTF 文鼎书宋繁.TTF 文鼎习字体.TTF 文鼎新艺体简.TTF 文鼎齿轮体.TTF 文鼎粗魏碑简.TTF 文鼎古印体繁.TTF 文鼎特粗黑简.TTF 文鼎细仿宋繁.TTF I don't know how to determine which font caused this problem -- 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.

2 3

[Bug 38673] New: valgrind shows uninitialized memory in dlls/kernel32/sync.c:ConnectNamedPipe()
by wine-bugs＠winehq.org 06 Feb '23

06 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=38673 Bug ID: 38673 Summary: valgrind shows uninitialized memory in dlls/kernel32/sync.c:ConnectNamedPipe() Product: Wine Version: 1.7.42 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase, valgrind Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Distribution: Fedora ../../../tools/runtest -q -P wine -T ../../.. -M hlink.dll -p hlink_test.exe.so hlink && touch hlink.ok ==14126== Thread 3: ==14126== Syscall param writev(vector[...]) points to uninitialised byte(s) ==14126== at 0x4F7A0F4B: ??? (in /usr/lib/libc-2.21.so) ==14126== by 0x7BC7A9C5: send_request (server.c:228) ==14126== by 0x7BC7AB52: wine_server_call (server.c:309) ==14126== by 0x7BC7B8CD: server_select (server.c:607) ==14126== by 0x7BC85426: NtWaitForMultipleObjects (sync.c:976) ==14126== by 0x7BC85471: NtWaitForSingleObject (sync.c:985) ==14126== by 0x7BC45DFF: server_ioctl_file (file.c:1539) ==14126== by 0x7BC46565: NtFsControlFile (file.c:1786) ==14126== by 0x7B87406B: ConnectNamedPipe (sync.c:1615) ==14126== by 0x49255A5: listen_thread (rpc_transport.c:132) ==14126== by 0x7BC81BB7: ??? (signal_i386.c:2682) ==14126== by 0x7BC81BFE: call_thread_func (signal_i386.c:2741) ==14126== by 0x7BC81B95: ??? (signal_i386.c:2682) ==14126== by 0x7BC88D78: start_thread (thread.c:443) ==14126== by 0x4F88F37F: start_thread (in /usr/lib/libpthread-2.21.so) ==14126== by 0x4F7ABD4D: clone (in /usr/lib/libc-2.21.so) ==14126== Address 0x4cee5c4 is on thread 1's stack ==14126== Uninitialised value was created by a stack allocation ==14126== at 0x7B873FA5: ConnectNamedPipe (sync.c:1601) ==14126== also shows in ieframe/webbrowser, kernel32/pipe, -- 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.

2 3

[Bug 48538] New: Cricut design space: crashes on installing
by WineHQ Bugzilla 05 Feb '23

05 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=48538 Bug ID: 48538 Summary: Cricut design space: crashes on installing Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: vo1xa.brad(a)gmail.com Distribution: --- Created attachment 66346 --> https://bugs.winehq.org/attachment.cgi?id=66346 output of error log Cricut design space fails to install encounters major error -- 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.

1 6

[Bug 45884] New: Just Cause 2 crashed at start
by wine-bugs＠winehq.org 05 Feb '23

05 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=45884 Bug ID: 45884 Summary: Just Cause 2 crashed at start Product: Wine Version: 3.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: legluondunet(a)free.fr Distribution: --- Created attachment 62390 --> https://bugs.winehq.org/attachment.cgi?id=62390 Just Cause 2 crashed at start terminal log Hello, Just Cause II crashed at start, you can reproduce this crash at each launch. I joined you the log terminal. Thank you for your help. LGDN. -- 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.

2 7

[Bug 50596] New: Sacred 2 crashes with D3DXCompileShader (d3dx9_36 builtin)
by WineHQ Bugzilla 05 Feb '23

05 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=50596 Bug ID: 50596 Summary: Sacred 2 crashes with D3DXCompileShader (d3dx9_36 builtin) Product: Wine Version: 6.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d-util Assignee: wine-bugs(a)winehq.org Reporter: berillions(a)gmail.com Distribution: --- Created attachment 69281 --> https://bugs.winehq.org/attachment.cgi?id=69281 +d3dx log Hi, The game crashes at launch with this trace before crash : ------ 0024:trace:d3dx:D3DXCompileShader data "#include \"ui_include.shader\"\n\n\nstruct pixdata {\n\tfloat4 hposition : POSITION;\n\tfloat4 texcoord0 : TEXCOORD0;\n\tfloat4 texcoord1 : TEXCOORD1;\n\tfloat4 texcoord2 : TEXCOORD2;\n\tfloat4 light_dir : TEXCOORD3;\n\tfloat4 color : COLOR;\n};\n\n\nstruct fragout {\n\tfloat4 col "..., length 1410, defines 00000000, include 0031E318, function "mainVS", profile "vs_1_1", flags 0, shader 0031E330, error_msgs 0031E310, constant_table 0031E308. ------ Set d3dx9_36 to native fix the issue. I attach +d3dx 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.

1 3

[Bug 40569] New: application crashes with exception in ddraw_allocate_handle (win98)
by wine-bugs＠winehq.org 05 Feb '23

05 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=40569 Bug ID: 40569 Summary: application crashes with exception in ddraw_allocate_handle (win98) Product: Wine Version: 1.9.9 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: o.dierick(a)piezo-forte.be Distribution: --- Created attachment 54407 --> https://bugs.winehq.org/attachment.cgi?id=54407 Terminal output (wine 1.9.9) I get a page fault in 32-bit code when starting a game in TOCA Touring Car Championship. This is an old game that requires windows version <= win98. The demo also has the bug. ---begin quote--- ... wine: Unhandled page fault on read access to 0x00000110 at address 0x7e7fcf1d (thread 0028), starting debugger... Unhandled exception: page fault on read access to 0x00000110 in 32-bit code (0x7e7fcf1d). ... Backtrace: =>0 0x7e7fcf1d ddraw_allocate_handle+0x1d(t=0x10c, object=0x15f960, type=DDRAW_HANDLE_MATERIAL) [/home/olivier/Projets/wine-builds/1.9.9_x86/dlls/ddraw/../../../wine-git/dlls/ddraw/main.c:118] in ddraw (0x0033f478) ... ---end quote--- This is with git wine 1.9.9-35-gbd2999d and no 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.

2 16

[Bug 51481] New: Why is the Epson printer printing blank pages?
by WineHQ Bugzilla 04 Feb '23

04 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=51481 Bug ID: 51481 Summary: Why is the Epson printer printing blank pages? 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: baroncorrz(a)gmail.com Distribution: --- Epson printer printing blank pages because there must be some problem related to the cartridge ink or the nozzle. The cartridge ink must have been depleted. You need to check the level of ink by comparing the ink level with the marker on the ink tank. If the ink level is low, then it means that you need to put in a new cartridge. If you have an ink tank with a low ink level, then fill the ink tank with the ink. The problem can also be due to the clogging of the nozzle. You need to clean the nozzle if this happens. One of the best ways to prevent this is by giving fewer jobs to the printer. https://www.epsonprintersupportpro.us/blog/printer-printing-blank-pages/ -- 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.

1 5

[Bug 50129] New: Calibre-portable error initializing the bypy frozen importer
by WineHQ Bugzilla 03 Feb '23

03 Feb '23

https://bugs.winehq.org/show_bug.cgi?id=50129 Bug ID: 50129 Summary: Calibre-portable error initializing the bypy frozen importer Product: Wine Version: 5.0.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bilbiliblus(a)gmail.com Distribution: --- When I try to run Calibre-portable.exe y have this message: There was an error initializing the bypy frozen importer: <class 'MemoryError'>: Traceback (most recent call last): File bypy-importer.py, line 250, in <module> File bypy-importer.py, line 195, in __init__ It only happens since Calibre changed to version 5 and on. This very morning I've tried with Calibre 5.3 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.

1 3