wine-bugs October 2020

wine-bugs@winehq.org

1 participants
6711 discussions

[Bug 46503] New: Call of Juarez has shadows issue
by wine-bugs＠winehq.org 09 Apr '21

09 Apr '21

https://bugs.winehq.org/show_bug.cgi?id=46503 Bug ID: 46503 Summary: Call of Juarez has shadows issue Product: Wine Version: 4.0 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: andrey.goosev(a)gmail.com Distribution: --- Created attachment 63354 --> https://bugs.winehq.org/attachment.cgi?id=63354 screenshot First thing is that no shadows at all until commit 56d4de0fdee57b0acf02399525a893cc1b42d759 After that shadows become visible/invisible while moving mouse. wine-4.0-52-gf5d7d9cccc -- 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 46573] New: Call of Duty 4 doesn't play multiplayer
by wine-bugs＠winehq.org 09 Apr '21

09 Apr '21

https://bugs.winehq.org/show_bug.cgi?id=46573 Bug ID: 46573 Summary: Call of Duty 4 doesn't play multiplayer Product: Wine Version: 3.0 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: directx-d3dx9 Assignee: wine-bugs(a)winehq.org Reporter: borisgopnik73(a)gmail.com Distribution: --- Unhandled exception: page fault on read access to 0x30303030 in 32-bit code (0x30303030). Register dump: CS:0023 SS:002b DS:002b ES:002b FS:006b GS:0063 EIP:30303030 ESP:0033f4d8 EBP:0033f4ec EFLAGS:00010216( R- -- I -A-P- ) EAX:00000000 EBX:00000000 ECX:00000003 EDX:00000008 ESI:0033f512 EDI:006cc274 Stack dump: 0x0033f4d8: 30303030 30303030 30303030 30303030 0x0033f4e8: 30303030 30303030 30303030 30303030 0x0033f4f8: 30303030 30303030 30303030 30303030 0x0033f508: 30303030 30303030 30303030 30303030 0x0033f518: 30303030 30303030 30303030 30303030 0x0033f528: 30303030 30303030 30303030 30303030 000d: sel=006f base=00000000 limit=00000000 16-bit r-x Backtrace: =>0 0x30303030 (0x0033f4ec) 0x30303030: -- no code accessible -- Modules: Module Address Debug info Name (39 modules) PE 400000- d936000 Deferred iw3mp PE d940000- dcaf000 Deferred d3dx9_34 PE 17f70000-17f86000 Deferred mileseq.flt PE 17f90000-17fa1000 Deferred msseax.flt PE 18000000-18033000 Deferred binkw32 PE 21100000-21197000 Deferred mss32 PE 22300000-22306000 Deferred mssds3d.flt PE 24100000-24112000 Deferred mssdsp.flt PE 26400000-2642a000 Deferred mssvoice.asi PE 26f00000-26f20000 Deferred mssmp3.asi PE 67030000-67105000 Deferred pbsv PE 67230000-67301000 Deferred pbcl PE 7a820000-7a824000 Deferred opengl32 PE 7b410000-7b5b6000 Deferred kernel32 PE 7bc10000-7bc14000 Deferred ntdll PE 7df60000-7df68000 Deferred oleaut32 PE 7e4e0000-7e4e3000 Deferred winepulse PE 7e740000-7e744000 Deferred mmdevapi PE 7ea80000-7ea83000 Deferred usp10 PE 7ed40000-7ed44000 Deferred winex11 PE 7edd0000-7edd4000 Deferred imm32 PE 7f040000-7f044000 Deferred ddraw PE 7f0c0000-7f0c8000 Deferred shlwapi PE 7f130000-7f292000 Deferred shell32 PE 7f380000-7f384000 Deferred dsound PE 7f3d0000-7f3d4000 Deferred msvcrt PE 7f480000-7f484000 Deferred wined3d PE 7f5c0000-7f5c4000 Deferred d3d9 PE 7f620000-7f624000 Deferred iphlpapi PE 7f650000-7f654000 Deferred ws2_32 PE 7f680000-7f684000 Deferred wsock32 PE 7f6a0000-7f6a9000 Deferred msacm32 PE 7f6d0000-7f6d4000 Deferred rpcrt4 PE 7f760000-7f788000 Deferred ole32 PE 7f8b0000-7f8b4000 Deferred advapi32 PE 7f920000-7f927000 Deferred gdi32 PE 7fa60000-7fb26000 Deferred user32 PE 7fc30000-7fca8000 Deferred winmm PE 7ffd0000-7ffd4000 Deferred version Threads: process tid prio (all id:s are in hex) 0000000e services.exe 00000029 0 00000024 0 0000001d 0 00000013 0 00000010 0 0000000f 0 00000011 winedevice.exe 0000001c 0 00000017 0 00000016 0 00000012 0 0000001a plugplay.exe 0000001f 0 0000001e 0 0000001b 0 00000020 PnkBstrA.exe 00000026 0 00000025 0 00000021 0 00000022 explorer.exe 00000030 0 0000002f 0 0000002e 0 00000023 0 00000027 winedevice.exe 00000031 0 0000002b 0 0000002a 0 00000028 0 00000047 (D) C:\Program Files (x86)\Activision\Call of Duty 4 - Modern Warfare\iw3mp.exe 00000057 0 00000056 0 00000055 0 00000054 0 00000053 0 00000052 0 00000051 0 00000050 15 0000004f 15 0000004b 15 0000004a 0 00000049 1 00000048 0 <== System information: Wine build: wine-3.0 (Ubuntu 3.0-1ubuntu1) Platform: i386 (WOW64) Version: Windows XP Host system: Linux Host version: 4.15.0-45-generic The problem is that some days ago, it worked well without any 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 6

[Bug 39156] New: magicka 2 doesn't start
by wine-bugs＠winehq.org 09 Apr '21

09 Apr '21

https://bugs.winehq.org/show_bug.cgi?id=39156 Bug ID: 39156 Summary: magicka 2 doesn't start 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: scrimekiler(a)yahoo.fr Distribution: --- Created attachment 52185 --> https://bugs.winehq.org/attachment.cgi?id=52185 +loaddll Hi, I have added Magicka 2 as new app on wine app db, it should come soon. The game doesn't start at all and I'm trying to figure out why.I run it in a 32 bits clean prefix. disabling d3d10 and d3d11 removes the error output about d3d.Adding vcrun2005 using winetricks removes the error about msvcrt (I've added this specific version because +loaddll shows it's trying to load msvcr80) Anyway, even after this the game still doesn't start.I've also tried to add the component for magicka 1 with winetricks in case it uses some common components without success (dotnet35 xna31 xinput) I've added the +loaddll log as attachement, but here is the default wine output : fixme:winediag:start_process Wine Staging 1.7.47 is a testing version containing experimental patches. fixme:winediag:start_process Please report bugs at http://bugs.wine-staging.com (instead of winehq.org). fixme:ole:RemUnknown_QueryInterface No interface for iid {00000019-0000-0000-c000-000000000046} fixme:console:AttachConsole stub ffffffff fixme:ver:GetCurrentPackageId (0x33fa38 (nil)): stub fixme:d3d11:D3D11CreateDevice adapter 0x13d6d0, driver_type D3D_DRIVER_TYPE_UNKNOWN, swrast (nil), flags 0, feature_levels 0x33f6e4, levels 0x6, sdk_version 7, device (nil), feature_level 0x33f6e0, context (nil) stub! err:ole:CoCreateInstance apartment not initialised fixme:msvcrt:__clean_type_info_names_internal (0x64085a64) stub -- 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 6

[Bug 43896] New: Elex renders most parts as big white glowing area
by wine-bugs＠winehq.org 08 Apr '21

08 Apr '21

https://bugs.winehq.org/show_bug.cgi?id=43896 Bug ID: 43896 Summary: Elex renders most parts as big white glowing area Product: Wine-staging Version: 2.18 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: holzminister(a)t-online.de CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 59514 --> https://bugs.winehq.org/attachment.cgi?id=59514 Terminal log, compressed; uncompressed size is 43 MB When I start up Elex(GOG version) most parts ingame are kind of glowing white/yellow/green and are overshadowing the game graphics(see screenshots). I can move ingame and collect things from the ground, but with the rendering bug it is more or less unplayable. -- 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 17

[Bug 46368] New: The game Evil Twin segfaults when loading saved state.
by wine-bugs＠winehq.org 08 Apr '21

08 Apr '21

https://bugs.winehq.org/show_bug.cgi?id=46368 Bug ID: 46368 Summary: The game Evil Twin segfaults when loading saved state. Product: Wine Version: 4.0-rc2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: inferrna(a)gmail.com Distribution: --- Created attachment 63107 --> https://bugs.winehq.org/attachment.cgi?id=63107 Bactrace in 4.02 (staging) I still can play the game in previous version of wine (stable 3.04) bot it fails in modern versions. -- 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 8

[Bug 45911] New: Rocksmith 2014 crashes after playing Score Attack
by wine-bugs＠winehq.org 08 Apr '21

08 Apr '21

https://bugs.winehq.org/show_bug.cgi?id=45911 Bug ID: 45911 Summary: Rocksmith 2014 crashes after playing Score Attack 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: milo(a)meelo.org Distribution: --- Created attachment 62440 --> https://bugs.winehq.org/attachment.cgi?id=62440 crashlog Rocksmith 2014/remastered (steam) crashes roughly 10 minutes after starting Score Attack mode, even if you play just one song in it and move on to Learn a Song mode. Reproducing the easiest way: * Go to Guitarcade -> Score Attack * Pick a song that's 4-5 minutes long * Play the same song until the game crashes ** Should crash during third playthrough Workaround: Restarting game client after every two playthroughs in Score Attack. Wine-prefix is 64bit. system: CPU: AMD FX(tm)-8320 Eight-Core Processor GPU: GeForce GTX 960 (2 GB video memory) nvidia-drivers-396.24 RAM: 16 GB OS: Gentoo, with 4.16.14 kernel Wine versions tested: wine-staging 3.9 - 3.16 -- 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 43969] New: openGL SwapBuffers with NULL context
by wine-bugs＠winehq.org 08 Apr '21

08 Apr '21

https://bugs.winehq.org/show_bug.cgi?id=43969 Bug ID: 43969 Summary: openGL SwapBuffers with NULL context Product: Wine Version: 2.19 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: jp-dev(a)inbox.ru Distribution: --- A fragment of openGL code works under Windows and crashes under wine staging 2.19 at glxdrv_wglSwapBuffers. This code can be found under the VSTGUI project (see https://git.io/vFCwl). The problem in wine is triggered because the library makes a null context current before the invocation of swapBuffers. As strange as it may be, Windows is able to render in this condition. wglMakeCurrent (deviceContext, 0); SwapBuffers (deviceContext); When I pass a context instead of 0, wine works as well. This reveals a pair of problems. First, there is a null pointer dereference in wgl_SwapBuffers. ctx->hdc is an invalid access because of the null context (I have added the `&& ctx` check). if (escape.gl_drawable && ctx) ExtEscape( ctx->hdc, X11DRV_ESCAPE, sizeof(escape), (LPSTR)&escape, 0, NULL ); This change allows the program to run without crash, but the result is no rendering. My test configuration on Windows was 8.1 with the vmware GL passthrough driver. -- 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 8

[Bug 17735] New: andrew rudson's drum machine: makes wine segfault upon start
by wine-bugs＠winehq.org 08 Apr '21

08 Apr '21

http://bugs.winehq.org/show_bug.cgi?id=17735 Summary: andrew rudson's drum machine: makes wine segfault upon start Product: Wine Version: 1.1.17 Platform: PC URL: http://andrewrudson.com/drummachine/main.php OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: timonator(a)perpetuum-immobile.de When starting up Drum Machine (see URL for download link; this bug report is for drum machine version "1.36 beta") Wine crashes with a Segfault like this: zsh: segmentation fault wine DrumMachine.exe I can briefly see a window pop up and immediately close again. -- 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 18

[Bug 46152] New: Ravage Lite VST plugin fails to register
by wine-bugs＠winehq.org 08 Apr '21

08 Apr '21

https://bugs.winehq.org/show_bug.cgi?id=46152 Bug ID: 46152 Summary: Ravage Lite VST plugin fails to register Product: Wine Version: 3.0.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wininet Assignee: wine-bugs(a)winehq.org Reporter: alexthebassist(a)yandex.ru Distribution: --- Created attachment 62792 --> https://bugs.winehq.org/attachment.cgi?id=62792 Terminal output I've got a legitimate license of Ravage Lite distortion plugin, but cannot register and get rid of trial period. Every time I try to use it, I get a stack overflow. Otherwise the plugin functions fine, despite multiple fixme warnings it throws out when run in a terminal. I'm using Carla as a host application and a wrapper for Ardour. System info: OS: KDE Neon 18.04 x86_64; Wine: wine-rt 3.0.2; Native overrides: winhttp and secur32. What can I do to investigate the problem further? -- 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 11

[Bug 44391] New: Star Trek Online: Hang when clicking "Engage"
by wine-bugs＠winehq.org 08 Apr '21

08 Apr '21

https://bugs.winehq.org/show_bug.cgi?id=44391 Bug ID: 44391 Summary: Star Trek Online: Hang when clicking "Engage" Product: Wine Version: 3.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mbt(a)fortifiedtechsystems.com Distribution: --- Updated to Wine 3.0 and decided to try STO to see if it would work. The upside is that it works better than it did when I tried it last time, but it still doesn't work. It patches (slowly, but it does finish), but when clicking the "Engage" button after the patch has done, the program blocks, never to be heard from again. Now, the debug output in total is too large to even really attach as a compressed archive of files, so I'm going to defer to waiting for a detailed request for information. However, what I _do_ know is that the program is blocking on a read of a pipe file descriptor that is apparently not ready. The pipe is created during program startup: pipe2([7, 8], O_CLOEXEC) = 0 And then (MUCH, MUCH LATER), when I click on the Engage button: write(3, "\v\1\0\0\0\0\0\0\0\0\0\0\234\1\0\0D\244\254E\0\0\0\0D\244\254E\0\0\0\0"..., 64) = 64 read(5, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 64) = 64 rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 rt_sigprocmask(SIG_BLOCK, [HUP INT USR1 USR2 ALRM CHLD IO], [], 8) = 0 writev(3, [{iov_base="\32\0\0\0000\0\0\0\0\0\0\0\2\0\0\0\330\3162\0\0\0\0\0\377\377\377\377\377\377\377\177"..., iov_len=64}, {iov_base="\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., iov_len=40}, {iov_base="\1\0\0\0\340\1\0\0", iov_len=8}], 3) = 112 read(5, "\3\1\0\0\0\0\0\0\377\377\377\377\377\377\377\177\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 64) = 64 rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 read(7, It will sit for _forever_ that way. (At that point, it is still the socket from earlier; I actually worked backwards from the fd number in /proc/$PID/fd/7 in order to figure out where it was instantiated in the log file.) The only way out of it is to kill the process, which then wraps out the log as thus: read(7, <unfinished ...>) = ? +++ killed by SIGKILL +++ At that point, of course, the program ends and Wine shuts back down. Retrial does the same time, and it does not appear to matter what version of Windows WINE is set to report. I would _love_ to report more information. But I need to be told what to gather to turn this into a _really_ useful bug report. STO is just about the only thing I boot up Windows for... it'd sure be nice to be rid of that requirement! Thanks, and keep up the good 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.

2 5

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs October 2020