wine-bugs May 2021

wine-bugs@winehq.org

1 participants
5533 discussions

[Bug 44681] New: Outcast Second Contact: Black screen
by wine-bugs＠winehq.org 23 Mar '22

23 Mar '22

https://bugs.winehq.org/show_bug.cgi?id=44681 Bug ID: 44681 Summary: Outcast Second Contact: Black screen Product: Wine Version: 3.3 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: sa(a)whiz.se Distribution: --- Created attachment 60690 --> https://bugs.winehq.org/attachment.cgi?id=60690 debug log in dx11 The game Outcast: Second Contact (from GOG) starts and runs but only shows a black screen. >From the logs 0033:fixme:d3d:wined3d_device_resolve_sub_resource Unhandled multisample resolve, dst_format WINED3DFMT_R8G8B8A8_TYPELESS, src_format WINED3DFMT_R8G8B8A8_TYPELESS, format WINED3DFMT_R8G8B8A8_UNORM. 0032:err:d3d:wined3d_debug_callback 0x77f1480: "GL_INVALID_ENUM in glTexSubImage2D(target=GL_TEXTURE_2D_MULTISAMPLE)". I'm guessing this is bug #39754 but filing a new one just to be sure. I also tried forcing the game to start in d3d9 mode by disabling the d3d11 dll. I have no idea if it works for this title, but is supported in some other Unity games. The behavior is similar, but the game shows a pink screen and logs: 0032:err:d3d:wined3d_debug_callback 0xd8810: "GL_INVALID_ENUM in glTexSubImage2D(target=GL_TEXTURE_2D_MULTISAMPLE)". Attaching logs from dx11 and dx9 runs. -- 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 51065] New: Star CItizen needs mountmgr.sys support for StorageDeviceSeekPenaltyProperty as an argument for query_property()
by WineHQ Bugzilla 23 Mar '22

23 Mar '22

https://bugs.winehq.org/show_bug.cgi?id=51065 Bug ID: 51065 Summary: Star CItizen needs mountmgr.sys support for StorageDeviceSeekPenaltyProperty as an argument for query_property() Product: Wine Version: 6.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mountmgr.sys Assignee: wine-bugs(a)winehq.org Reporter: spambox1(a)koolhoven-home.net Distribution: --- Created attachment 69927 --> https://bugs.winehq.org/attachment.cgi?id=69927 Implements StorageDeviceSeekPenaltyProperty as an argument for query_property() New version of Star Citizen needs to know if it's operating on a drive with a seek penalty. -- 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 12

[Bug 50932] New: Warlords Battlecry II crashes on create hero
by WineHQ Bugzilla 23 Mar '22

23 Mar '22

https://bugs.winehq.org/show_bug.cgi?id=50932 Bug ID: 50932 Summary: Warlords Battlecry II crashes on create hero Product: Wine Version: 6.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: 9xzsnuwq9h(a)snkmail.com Distribution: --- Created attachment 69748 --> https://bugs.winehq.org/attachment.cgi?id=69748 crash log Start, select skirmish or campaign, create a race, put a hero name, confirm => crash (see full attached) Unhandled exception: page fault on read access to 0x305b0a77 in 32-bit code (0x005dd183 This seems to be an regression from wine 4.0 (have not tried both on the same hardware though). Will provide more info as soon as I find the time. -- 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 46402] New: DnsQuery_W fails for DNS_TYPE_ANY
by wine-bugs＠winehq.org 23 Mar '22

23 Mar '22

https://bugs.winehq.org/show_bug.cgi?id=46402 Bug ID: 46402 Summary: DnsQuery_W fails for DNS_TYPE_ANY Product: Wine Version: 4.0-rc3 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: dnsapi Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- Fluenz calls DnsQuery_W with DNS_TYPE_ANY, and this fails - then it assumes there is no internet. The underlying problem is that res_query fails for T_ANY - not sure why, but it's like that. Forcing res_query to use T_A works around the problem and makes Fluenz 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 6

[Bug 35815] New: Allow remapping of joystick buttons
by wine-bugs＠winehq.org 23 Mar '22

23 Mar '22

http://bugs.winehq.org/show_bug.cgi?id=35815 Bug ID: 35815 Summary: Allow remapping of joystick buttons Product: Wine Version: 1.7.14 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: directx-dinput Assignee: wine-bugs(a)winehq.org Reporter: achurch+wine(a)achurch.org Some Windows games only accept a limited number of joystick button inputs, presumably based on the set of joystick devices against which the game was tested. If the native driver for a device returns different button numbers than the Windows driver, this can prevent some common controller devices from being used with such games. For example, the PlayStation 3 controller reports its face buttons as button numbers 12-15, but apparently the commonly used Windows driver "MotioninJoy" remaps these to lower button numbers; due to that, some games (such as Astebreed: http://edelweiss.skr.jp/works/astebreed/) only accept up to 12 button inputs, preventing PS3 controllers from working properly. The attached patch (against Wine 1.7.14) adds a "ButtonMap" configuration value to the DirectInput registry key, allowing the first 16 joystick button inputs reported by Wine to be remapped to arbitrary native joystick buttons. The format of the value is a comma-separated list of numbers, with the first number giving the (zero-based) physical button index for DirectInput button 0, the second number giving the physical button index for DirectInput button 1, and so on for up to 16 buttons. -- 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 27

[Bug 49884] New: When transitioning from Useful Registry Keys to Wine Man Page - 404 Page Not Found Error
by WineHQ Bugzilla 23 Mar '22

23 Mar '22

https://bugs.winehq.org/show_bug.cgi?id=49884 Bug ID: 49884 Summary: When transitioning from Useful Registry Keys to Wine Man Page - 404 Page Not Found Error 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: commissaris.mike(a)gmail.com Distribution: --- Clicked on Wine Man Page at bottom of Useful Registry Keys page and the result was page not found. Broken link? -- 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 2

[Bug 49754] New: Invalid write of size 4 - while clearing thread stack
by WineHQ Bugzilla 23 Mar '22

23 Mar '22

https://bugs.winehq.org/show_bug.cgi?id=49754 Bug ID: 49754 Summary: Invalid write of size 4 - while clearing thread stack Product: Wine Version: 5.16 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: jeffersoncarpenter2(a)gmail.com Distribution: --- Created attachment 68058 --> https://bugs.winehq.org/attachment.cgi?id=68058 Valgrind output Occurs as of 5bb27d1edb2. Steps to reproduce: * Build 'int main() { return 0; }' using i686-w64-mingw32-gcc. * Run wine under valgrind (valgrind output attached). Valgrind output snippet: ==9636== Invalid write of size 4 ==9636== at 0x7BC7AA17: ??? (signal_i386.c:470) ==9636== Address 0x61bab0 is on thread 1's stack -- 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 49914] New: Windows CLI has error with text highlighting
by WineHQ Bugzilla 22 Mar '22

22 Mar '22

https://bugs.winehq.org/show_bug.cgi?id=49914 Bug ID: 49914 Summary: Windows CLI has error with text highlighting Product: Wine Version: 5.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: shagooserver(a)gmail.com Distribution: --- Created attachment 68285 --> https://bugs.winehq.org/attachment.cgi?id=68285 example The latest version of wine extends the highlight colour of a windows terminal command to far. In the attached example the green highlight should only cover the word "Done" or that line only. What happens though is that the highlight extends through to the following command prompt. Although not shown in the example but also occurring is the intervening blank line between "Done" and the following command prompt is also green highlighted. -- 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 11112] New: Does the fatal error if the config directory isn' t owned by the user make sense?
by wine-bugs＠winehq.org 21 Mar '22

21 Mar '22

http://bugs.winehq.org/show_bug.cgi?id=11112 Summary: Does the fatal error if the config directory isn't owned by the user make sense? Product: Wine Version: CVS/GIT Platform: All OS/Version: All Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: bero(a)arklinux.org Created an attachment (id=10147) --> (http://bugs.winehq.org/attachment.cgi?id=10147) Proposed fix Recent wine versions abort on startup if the config directory isn't owned by the user running wine. This breaks setups where several users share a common wine prefix (e.g. to make applications that make heavy use of the registry available to several users without installing them several times) and they have the right access to the configs through group permissions. Unless I'm overlooking a better way to do this, it would make more sense to check proper permissions than to check ownership. I'm attaching a patch that does that. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

2 50

[Bug 25773] New: Majesty 2: certain keyboard keys are not recognized
by wine-bugs＠winehq.org 19 Mar '22

19 Mar '22

http://bugs.winehq.org/show_bug.cgi?id=25773 Summary: Majesty 2: certain keyboard keys are not recognized Product: Wine Version: 1.3.11 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: gyebro69(a)gmail.com Created an attachment (id=32841) --> (http://bugs.winehq.org/attachment.cgi?id=32841) terminal output I noticed the problem when trying to start a multiplayer game. Logging in to Gamespy requires an email address but the period '.' sign used in the address was not accepted in the input field. It turned out that several other keys are not recognized by the game, e.g.: ~,[]/;'\=-+. By default '~' is used to bring up the chat window. The issue can be tested by creating a new profile in the game: the input field, containing the name, should accept all of the above mentioned characters but they're not recognized (only the letters and numbers work and some of the special characters by using <Shift>: @!$%). Installing native dinput8.dll (via winetricks) doesn't help in Majesty 2. Fedora 14 / Gnome 2.32.0 / xorg-x11-server 1.9.3-3.fc14 -- 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 8

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