wine-bugs January 2021

wine-bugs@winehq.org

1 participants
6901 discussions

[Bug 49186] New: DXBC compiler generates incorrect spir-v code
by WineHQ Bugzilla 27 May '21

27 May '21

https://bugs.winehq.org/show_bug.cgi?id=49186 Bug ID: 49186 Summary: DXBC compiler generates incorrect spir-v code Product: vkd3d Version: 1.1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: vkd3d Assignee: wine-bugs(a)winehq.org Reporter: alex.fishman(a)gmail.com Distribution: --- Created attachment 67204 --> https://bugs.winehq.org/attachment.cgi?id=67204 dxbc tessellaton control shader I'm having issues with tessellation shaders. Seems that the generated spir-v code is incorrect. After converting the spir-v to GLSL (spirv-dis) and validating it (glslangValidator) there are errors in the the following section: #version 450 layout(vertices = 5) out; out float gl_ClipDistance[5]; layout(location = 0) out vec2 o0[5]; layout(location = 1) out vec4 o1[5]; vec4 opc[4]; vec4 v1[5]; void control0() { v1[1u] = vec4(gl_ClipDistance[0u]); v1[2u] = vec4(gl_ClipDistance[1u]); v1[3u] = vec4(gl_ClipDistance[2u]); v1[4u] = vec4(gl_ClipDistance[3u]); v1[5u] = vec4(gl_ClipDistance[4u]); vec4 r0; r0.x = intBitsToFloat(gl_InvocationID); o0[gl_InvocationID] = gl_in[floatBitsToInt(r0.x)].gl_Position.xy; o1[gl_InvocationID] = v1[floatBitsToInt(r0.x)]; } ... glslangValidator outputs the following error: ERROR: 0:4: 'gl_ClipDistance' : identifiers starting with "gl_" are reserved ERROR: 1 compilation errors. No code generated. Sample DXBC binary 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.

1 6

[Bug 49301] New: pthread_exit hangs on unwind through call_thread_exit_func on arm64
by WineHQ Bugzilla 26 May '21

26 May '21

https://bugs.winehq.org/show_bug.cgi?id=49301 Bug ID: 49301 Summary: pthread_exit hangs on unwind through call_thread_exit_func on arm64 Product: Wine Version: unspecified Hardware: aarch64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: stefan(a)codeweavers.com Distribution: --- Created attachment 67309 --> https://bugs.winehq.org/attachment.cgi?id=67309 Workaround My arm64 Wine build spins in services.exe after starting up anything. The backtrace points into pthread_exit() - see attached file backtrace.txt. I placed pthread_exit calls throughout the thread creation / shutdown code and it works up to the point where signal_exit_thread() calls call_thread_exit_func(). After call_thread_exit_func() passes control to the C function exit_thread() pthread_exit() will hang. I previously had this problem only in a gcc wine build (with 8fb8cc03 reverted), but recently, presumably after an update to clang-10, the problem also happens when building Wine with clang. The attached backtrace is from a build with clang 10. Calling exit_thread() directly from signal_exit_thread() without going through call_thread_exit_func works around the problem. See attached file noasm.diff -- 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 4

[Bug 49378] New: kernel32.WriteFile with multi byte characters reports incorrect number of written bytes
by WineHQ Bugzilla 26 May '21

26 May '21

https://bugs.winehq.org/show_bug.cgi?id=49378 Bug ID: 49378 Summary: kernel32.WriteFile with multi byte characters reports incorrect number of written bytes Product: Wine Version: 5.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: suokkos(a)gmail.com Distribution: --- Created attachment 67438 --> https://bugs.winehq.org/attachment.cgi?id=67438 Wine test case to trigger the bug Writing utf-8 multibyte characters to stdout using stdio led to uncovering this bug. Attached test case is a simple way to trigger the underlying issue. Minimal steps leading to issue: 1. Set console output to CP_UTF8 2. Use WriteFile with multibyte characters Expect outcome: WriteFile reports number of bytes written. Actual outcome: WriteFile reports number of characters written. Other observations while writing test case: I first run same test case using kernelbase.WriteFile. Base version seems to behavior differently because my test case passed. I only then noticed the important detail that there is multiple WriteFile entry points. -- 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 45110] New: Crash when running courselab 2.4
by wine-bugs＠winehq.org 26 May '21

26 May '21

https://bugs.winehq.org/show_bug.cgi?id=45110 Bug ID: 45110 Summary: Crash when running courselab 2.4 Product: Wine Version: 1.6.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cjrw42(a)gmail.com Distribution: --- Created attachment 61295 --> https://bugs.winehq.org/attachment.cgi?id=61295 courselab 2.4 backtrace I have installed courselab 2.4 (educational resource dev package which creates HTML based sites), using the MSI, and all appears to have gone OK. Courselab runs, grabs credentials, generates the licence key which is emailed and entered fine, but as soon as you begin to create a new project it crashes out. backtrace included. -- 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

[Bug 40223] New: Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth texture)
by wine-bugs＠winehq.org 26 May '21

26 May '21

https://bugs.winehq.org/show_bug.cgi?id=40223 Bug ID: 40223 Summary: Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth texture) Product: Wine Version: 1.9.4 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ovariegata(a)yahoo.com Distribution: Slackware When starting the GOG version of Deus Ex with wine-staging 1.9.4 and a debug version of mesa this error is printed several times. Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth texture) Here is the full output: $ deusex preloader: Warning: failed to reserve range 00010000-00110000 preloader: Warning: failed to reserve range 00010000-00110000 fixme:winediag:start_process Wine Staging 1.9.4 is a testing version containing experimental patches. fixme:winediag:start_process Please mention your exact version when filing bug reports on winehq.org. preloader: Warning: failed to reserve range 00010000-00110000 preloader: Warning: failed to reserve range 00010000-00110000 preloader: Warning: failed to reserve range 00010000-00110000 preloader: Warning: failed to reserve range 00010000-00110000 preloader: Warning: failed to reserve range 00010000-00110000 fixme:module:load_dll Loader redirect from L"uxtheme.dll" to L"uxtheme-gtk.dll" fixme:msg:pack_message msg 14 (WM_ERASEBKGND) not supported yet fixme:process:GetProcessWorkingSetSize (0xffffffff,0x32f314,0x32f30c): stub Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth texture) Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth texture) Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth texture) Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth texture) Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth texture) Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth texture) Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth texture) Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth texture) Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth texture) Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth texture) Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth texture) Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth texture) Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth texture) Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth texture) Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth texture) Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth texture) Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth texture) Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth texture) Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth texture) Mesa: User error: GL_INVALID_OPERATION in glTexImage3D(bad target for depth texture) err:ole:CoGetClassObject class {92fa2c24-253c-11d2-90fb-006008a1f441} not registered err:ole:CoGetClassObject no class object {92fa2c24-253c-11d2-90fb-006008a1f441} could be created for context 0x1 err:ole:CoGetClassObject class {d8f1eee0-f634-11cf-8700-00a0245d918b} not registered err:ole:CoGetClassObject no class object {d8f1eee0-f634-11cf-8700-00a0245d918b} could be created for context 0x1 fixme:winediag:IKsPropertySetImpl_QuerySupport EAX sound effects are enabled - try to disable it if your app crashes unexpectedly fixme:ddraw:ddraw7_FlipToGDISurface iface 0x16e2a8 stub! OS: Slackware-current Relevant packages: wine-staging-1.9.4-x86_64-1_SBo mesa-compat32-847f1cc_2015.12.16_master-x86_64-1_gitcompat32 libdrm-compat32-4274539_2016.02.26_master-x86_64-1_gitcompat32 -- 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 43433] New: Sony Vegas Pro 8
by wine-bugs＠winehq.org 26 May '21

26 May '21

https://bugs.winehq.org/show_bug.cgi?id=43433 Bug ID: 43433 Summary: Sony Vegas Pro 8 Product: Wine Version: 2.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bameylan(a)bluewin.ch Distribution: --- Created attachment 58799 --> https://bugs.winehq.org/attachment.cgi?id=58799 Backtrace genered at the crash This are the problems I encountered I am using Linux Mint 18.2 x64. I installed Sony Vegas Pro 8.0 on wine 2.13. Installation without problem. But when I tried to run it, it stop at the moment that he "Adding GStreamer AudioConvert filter" -- 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 2

[Bug 49583] New: Assassin's Creed Odyssey displays black bars on top and bottom.
by WineHQ Bugzilla 26 May '21

26 May '21

https://bugs.winehq.org/show_bug.cgi?id=49583 Bug ID: 49583 Summary: Assassin's Creed Odyssey displays black bars on top and bottom. Product: Wine Version: 5.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: GloriousEggroll(a)gmail.com Distribution: --- Created attachment 67739 --> https://bugs.winehq.org/attachment.cgi?id=67739 AC Odyssey black bar fix It's been a long known issue that AC: Odyssey renders with black bars on the top and bottom of the screen (see screenshot 1). Derek Lesho came up with a stub patch that both fixed this -and- allowed STEEP to run (it would not display previously). That patch can be found here: https://github.com/GloriousEggroll/proton-ge-custom/blob/5.12-GE-1/patches/… Recently, the relevant function QueryDisplayConfig was implemented, however it did not contain some of the changes Derek's patch adds. This allowed steep to work, however AC: Odyssey still retained the black bar issue. I modified Derek's patch by adding the relevant parts to QueryDisplayConfig, and removing the relevant flag checks (Derek's patch did this previously), and this allowed AC: Odyssey to render properly without the black bars. (see screenshot 2). The patch is hacky but may provide more information towards fixing this properly. -- 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 8

[Bug 49748] New: Multisim 14.2 installer fails with "Directory name invalid"
by WineHQ Bugzilla 25 May '21

25 May '21

https://bugs.winehq.org/show_bug.cgi?id=49748 Bug ID: 49748 Summary: Multisim 14.2 installer fails with "Directory name invalid" Product: Wine Version: 5.15 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- When running the installer, it terminates with a MessageBox showing "Directory name invalid". -- 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 8

[Bug 49788] New: mountmgr is no longer detecting SCSI devices
by WineHQ Bugzilla 25 May '21

25 May '21

https://bugs.winehq.org/show_bug.cgi?id=49788 Bug ID: 49788 Summary: mountmgr is no longer detecting SCSI devices Product: Wine Version: 5.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: mountmgr.sys Assignee: wine-bugs(a)winehq.org Reporter: winebugzilla(a)tasossah.com Regression SHA1: 19549d11a72f63efe0d689374446a56a68264a1f Distribution: --- Created attachment 68104 --> https://bugs.winehq.org/attachment.cgi?id=68104 regedit screenshot Commit 19549d11a72f63efe0d689374446a56a68264a1f switched to using udisks2 to detect devices, however this no longer detects SCSI devices. This results in ASPI_GetNumControllers always returning 0, and ASPI applications not detecting any optical drives. Compiling wine one commit before the one mentioned above (8388ea840fedbb9b646213a26cd59ceb3a48680b) restores the ability to detect and use SCSI devices. Tested on two different Ubuntu 20.04 installations, both with fully functional udisks2. Steps to reproduce: Start up wine regedit Navigate to HKLM\Hardware\DEVICEMAP\Scsi Observe that it is empty When functioning correctly, it should report all SCSI devices, including hard disks and optical drives. In general, all devices that exist in /proc/scsi/scsi should show up in the registry. https://bugs.winehq.org/show_bug.cgi?id=31592 was opened presumably to move away from /proc/scsi, however it is now a 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.

1 12

[Bug 49825] New: GetNamedSecurityInfoA with LABEL_SECURITY_INFORMATION returns ERROR_ACCESS_DENIED
by WineHQ Bugzilla 25 May '21

25 May '21

https://bugs.winehq.org/show_bug.cgi?id=49825 Bug ID: 49825 Summary: GetNamedSecurityInfoA with LABEL_SECURITY_INFORMATION returns ERROR_ACCESS_DENIED Product: Wine Version: 5.16 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: advapi32 Assignee: wine-bugs(a)winehq.org Reporter: vladimir.kokovic(a)gmail.com Distribution: --- Created attachment 68159 --> https://bugs.winehq.org/attachment.cgi?id=68159 wine log file Hi, I don't understand at all what this is all about even though I have a complete WINEDEBUG log, when it comes to GetNamedSecurityInfoA with LABEL_SECURITY_INFORMATION where ERROR_ACCESS_DENIED returns. Although at first glance everything is normal, it is obvious that I do not know enough wine and that is why I need help to resolve this situation and if possible remove this bug for the sake of others and not just me. Attached are 2 files: 1. TestGetNamedSecurityInfoA.cpp - test program 2. WINEDEBUG.log - part of a very large log file -- 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 9

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