wine-bugs June 2021

wine-bugs@winehq.org

1 participants
5128 discussions

[Bug 44249] New: Can't play Diablo 2 (Battle.net) when Virtualization in BIOS is disabled.
by wine-bugs＠winehq.org 08 Jan '22

08 Jan '22

https://bugs.winehq.org/show_bug.cgi?id=44249 Bug ID: 44249 Summary: Can't play Diablo 2 (Battle.net) when Virtualization in BIOS is disabled. Product: Wine Version: 2.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: asriroc(a)gmail.com Distribution: --- 1. I have "Virtualization" as "Enable" in my BIOS (Compaq Presario F763NR Notebook with the most recent BIOS version). 2. I installed a fresh Fedora 27 Cinnamon Spin with Linux 4.14.8-300.fc27.x86_64 kernel. 3. I installed NVIDIA 304.137 4. I installed Diablo 2 using WINE 2.22 At this point, I would be able to play Diablo 2 using Battle.net 5. I rebooted the notebook, and set "Disable" on the "Virtualization" in my BIOS. 6. I tried to play Diablo 2, using WINE 2.22, but I won't be able to use Battle.net Now, if I rebooted and enabled my virtualization in my BIOS, Diablo 2 would work again. Thank you so much. -- 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 9

[Bug 42223] New: I cant install AB Bulkmailer .. Please HELP me ...
by wine-bugs＠winehq.org 08 Jan '22

08 Jan '22

https://bugs.winehq.org/show_bug.cgi?id=42223 Bug ID: 42223 Summary: I cant install AB Bulkmailer .. Please HELP me ... Product: Wine Version: 2.0-rc4 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bluebird456(a)vfemail.net Distribution: --- Created attachment 56863 --> https://bugs.winehq.org/attachment.cgi?id=56863 AB BulkMailer install BUG I want to install AB BulkMailer . Which is a Windows app . I tried to install the app , But error appears ... I attached the detail in attached TEXT FILE ... Please CHECK and PLEASE HELP ME .. Please Fix the error BUG as soon as possible ... I JUST want to use the app ... -- 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 63

[Bug 39787] New: Lilos Lesewelt 2 crashes
by wine-bugs＠winehq.org 08 Jan '22

08 Jan '22

https://bugs.winehq.org/show_bug.cgi?id=39787 Bug ID: 39787 Summary: Lilos Lesewelt 2 crashes Product: Wine Version: 1.8-rc3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alois.schloegl(a)gmail.com Distribution: --- Created attachment 53081 --> https://bugs.winehq.org/attachment.cgi?id=53081 backtrack file, run with WINEDEBUG=+all "Lilos Lesewelt 2" can be installed, but when trying to start it, it crashes. The full debug log with WINEDEBUG=+all is available from (11MB !) http://pub.ist.ac.at/~schloegl/wine-reports/lilo2.debug.all.log.gz A short version for WINEDEBUG=+cdrom in http://pub.ist.ac.at/~schloegl/wine-reports/lilo2.debug.cdrom.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.

2 15

[Bug 35883] New: Horizon crashes with page fault
by wine-bugs＠winehq.org 08 Jan '22

08 Jan '22

http://bugs.winehq.org/show_bug.cgi?id=35883 Bug ID: 35883 Summary: Horizon crashes with page fault Product: Wine Version: 1.7.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jmelton116(a)gmail.com Created attachment 47912 --> http://bugs.winehq.org/attachment.cgi?id=47912 Backtrace generated by crash Horizon seems to crash at random times with a page fault. There seems to be no sort of consistency between what is occuring in game and when these occur, but I could be wrong. These were encountered on the latest git version. Page fault's backtrace is attached. -- 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 44146] New: Crysis 2: DX11 is a slideshow
by wine-bugs＠winehq.org 08 Jan '22

08 Jan '22

https://bugs.winehq.org/show_bug.cgi?id=44146 Bug ID: 44146 Summary: Crysis 2: DX11 is a slideshow Product: Wine Version: 3.0-rc1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: christian.frank(a)gmx.de Distribution: --- Hi, trying to play Crysis 2 with DX11 is actually impossible, it is a complete slideshow. Switching from DX9 to DX11 the FPS drop from ~ 40 to ~ 8 fps. Tons of fixmes are spit out: 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[31]" might be used before being initialized 0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render target 4. 0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render target 5. 0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render target 6. 0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render target 7. 0048:fixme:d3d_shader:print_glsl_info_log Info log received from GLSL shader #24: 0048:fixme:d3d_shader:print_glsl_info_log Vertex info 0048:fixme:d3d_shader:print_glsl_info_log ----------- 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[1]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[2]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[3]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[4]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[5]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[6]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[7]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[8]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[9]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[10]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[11]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[12]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[13]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[14]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[15]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[16]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[17]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[18]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[19]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[20]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[21]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[22]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[23]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[24]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[25]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[26]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[27]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[28]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[29]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[30]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[31]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0048:fixme:d3d_shader:print_glsl_info_log Fragment info 0048:fixme:d3d_shader:print_glsl_info_log ------------- 0048:fixme:d3d_shader:print_glsl_info_log 0(24) : warning C7050: "R0.yzw" might be used before being initialized 0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render target 4. 0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render target 5. 0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render target 6. 0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render target 7. 0048:fixme:d3d_shader:shader_sm4_read_instruction_modifier Unhandled modifier 0x800000c2. 0048:fixme:d3d_shader:shader_sm4_read_instruction_modifier Unhandled modifier 0x00155543. 0048:fixme:d3d_shader:print_glsl_info_log Info log received from GLSL shader #27: 0048:fixme:d3d_shader:print_glsl_info_log Vertex info 0048:fixme:d3d_shader:print_glsl_info_log ----------- 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[1].zw" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[2]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[3]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[4]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[5]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[6]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[7]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[8]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[9]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[10]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[11]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[12]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[13]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[14]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[15]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[16]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[17]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[18]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[19]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[20]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[21]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[22]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[23]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[24]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[25]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[26]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[27]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[28]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[29]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[30]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050: "vs_out[31]" might be used before being initialized 0048:fixme:d3d_shader:print_glsl_info_log 0048:fixme:d3d_shader:print_glsl_info_log Fragment info 0048:fixme:d3d_shader:print_glsl_info_log ------------- 0048:fixme:d3d_shader:print_glsl_info_log 0(26) : warning C7050: "R0.yzw" might be used before being initialized 0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render target 4. 0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render target 5. 0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render target 6. 0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render target 7. My GPU: Nvidia GTX 970 (384.98) Memory: 16GB CPU: Core i5 3570k Opensuse Tumbleweed, latest Snapshot Many thanks ! Christian -- 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 13

[Bug 22755] New: Regression : win16 installer program of "de rouck" freeze
by wine-bugs＠winehq.org 08 Jan '22

08 Jan '22

http://bugs.winehq.org/show_bug.cgi?id=22755 Summary: Regression : win16 installer program of "de rouck" freeze Product: Wine Version: 0.9.31. Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: vincent.hardy.be(a)gmail.com Created an attachment (id=28058) --> (http://bugs.winehq.org/attachment.cgi?id=28058) wine-1.1.31 screenshot It works with wine-1.1.30. With wine-1.1.31, see screenshot Regression test says : 3b1186de5aeabd261e70dab8b78a730030075ca1 is the first bad commit commit 3b1186de5aeabd261e70dab8b78a730030075ca1 Author: Alexandre Julliard <julliard(a)winehq.org> Date: Wed Oct 7 17:14:10 2009 +0200 kernel32: Move the 16-bit string functions to kernel16.c. :040000 040000 3412021b8c21c250ee3ccc60ce31c3f3f9365c50 3c5be0f4e2330e28e86e4b839447d40d88bf42f3 M dlls -- 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 11

[Bug 47189] New: Vortex doesn't start
by wine-bugs＠winehq.org 08 Jan '22

08 Jan '22

https://bugs.winehq.org/show_bug.cgi?id=47189 Bug ID: 47189 Summary: Vortex doesn't start Product: Wine Version: 4.6 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: logicalman101(a)gmail.com Distribution: --- Vortex doesn't run past installation phase no matter what version of dotnet I have installed. -- 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 22

[Bug 44822] New: Warframe can't update / game can't run
by wine-bugs＠winehq.org 08 Jan '22

08 Jan '22

https://bugs.winehq.org/show_bug.cgi?id=44822 Bug ID: 44822 Summary: Warframe can't update / game can't run Product: Wine Version: 3.4 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: vblanton(a)gmail.com Distribution: --- Warframe can't get past updating process, hence game won't start. This is a fresh install. Installs fine via steam. Starts with workarounds: winetricks: d3dx9 wininet winhttp xact hosts corefonts fontfix vcrun2015 Updating fails with the message "Update Failed! The content servers are temporarily" No workarounds have fixed this so far. Attempts to install other Visual C++ packages haven't helped. Various DLL overrides haven't helped. -- 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 13

[Bug 33131] New: taskkill doesn't support /fi (filtering) option
by wine-bugs＠winehq.org 08 Jan '22

08 Jan '22

http://bugs.winehq.org/show_bug.cgi?id=33131 Bug #: 33131 Summary: taskkill doesn't support /fi (filtering) option Product: Wine Version: 1.5.25 Platform: x86-64 OS/Version: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: programs AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com Blocks: 33130 Classification: Unclassified Noticed while looking at bug 33130 0067:Call KERNEL32.CreateProcessW(00000000,008fcb00 L"C:\\windows\\system32\\taskkill.exe /F /Fi \"MODULES eq AutoupdatePlugin.cpl\" /T",00000000,00000000,00000000,00000400,00000000,00000000,008fb1fc,008fb240) ret=7e4d517f -- 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 3

[Bug 24169] New: QuarkXPress version 8.x hangs on start (missing double quoting of browser path in HKCR\htmlfile\shell\open\command)
by wine-bugs＠winehq.org 08 Jan '22

08 Jan '22

http://bugs.winehq.org/show_bug.cgi?id=24169 Summary: QuarkXPress version 8.x hangs on start (missing double quoting of browser path in HKCR\htmlfile\shell\open\command) Product: Wine Version: 1.3.1 Platform: x86 URL: http://downloads.quark.com/Details.aspx?fid=163&&mid=2 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: focht(a)gmx.net Hello, someone in appdb reported QuarkXPress version 8.x (2010 version) hangs on start. Downloaded a 60-day trial ... it does indeed - due to a Wine shortcoming and an application bug. ;-) Basically the app retrieves default browser setting from registry and does some parsing to extract browser (unquoting and splitting '\' '/' path delimiter). Their parsing is broken in a way that it can't cope with missing double quotes around browser path leading to endless looping. HKEY_CLASSES_ROOT\htmlfile\shell\open\command -> C:\windows\system32\winebrowser.exe -nohome With the browser path in double quotes, QuarkXPress 8 starts fine. "C:\windows\system32\winebrowser.exe" -nohome The quoting is most likely present in Windows as the app would loop there too without. Regards -- 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 4

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 June 2021