October 2017 - Wine-Bugs - list.winehq.org

[Bug 34266] 0*inf in D3D9 shaders outputs NaNs to floating-point framebuffers

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=34266 Fabian Maurer <dark.shadow4(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4(a)web.de --- Comment #19 from Fabian Maurer <dark.shadow4(a)web.de> --- Does this issue still exist as of wine 2.20? -- 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.

Oct. 31, 2017

[Bug 42284] Enable using Wine with Wayland and without X on Linux

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=42284 jonwsb(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jonwsb(a)gmail.com -- 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.

Oct. 31, 2017

[Bug 43750] USB "ttyACM0" serial port not being created

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=43750 Alex Henrie <alexhenrie24(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |c296e7de4d6d7eab56ab3ee5d8f | |2dc2c913ae05f Resolution|--- |FIXED Component|-unknown |mountmgr.sys Status|UNCONFIRMED |RESOLVED --- Comment #3 from Alex Henrie <alexhenrie24(a)gmail.com> --- Sorry about that, and thanks for the bug report. I didn't realize that in a 64-bit Wine installation, you had to use 64-bit regedit (i.e. `wine64 regedit`) to edit the key. This has been fixed in Wine 2.20, so you will be able to use regular (32-bit) regedit from now on. Thanks again for pointing out the 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.

Oct. 31, 2017

[Bug 43948] d3dx9 effects - pixel shader 2.0 does not render well

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=43948 Jan Havran <havran.jan(a)email.cz> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |havran.jan(a)email.cz -- 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.

Oct. 31, 2017

[Bug 43948] d3dx9 effects - pixel shader 2.0 does not render well

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=43948 --- Comment #2 from Jan Havran <havran.jan(a)email.cz> --- Created attachment 59589 --> https://bugs.winehq.org/attachment.cgi?id=59589 d3d_shader debug Added disassembled HLSL and generated GLSL (output from WINEDEBUG=d3d_shader) -- 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.

Oct. 31, 2017

[Bug 43948] d3dx9 effects - pixel shader 2.0 does not render well

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=43948 Jan Havran <havran.jan(a)email.cz> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #59587|0 |1 is obsolete| | --- Comment #1 from Jan Havran <havran.jan(a)email.cz> --- Created attachment 59588 --> https://bugs.winehq.org/attachment.cgi?id=59588 d3dx9 efects -- 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.

Oct. 31, 2017

[Bug 43948] New: d3dx9 effects - pixel shader 2.0 does not render well

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=43948 Bug ID: 43948 Summary: d3dx9 effects - pixel shader 2.0 does not render well Product: Wine Version: 2.19 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3dx9 Assignee: wine-bugs(a)winehq.org Reporter: havran.jan(a)email.cz Distribution: ArchLinux Created attachment 59587 --> https://bugs.winehq.org/attachment.cgi?id=59587 d3dx9 effects I have strange behaviour of effects in d3dx9 application where I have access to source code. I tried to reduce code size to the minimum where this bug is still reproduciable. The problem is, when I apply attached shaders.fx effects (VS + PS) on some objects (triangle for example), then the object is black in Wine, while in Windows or Gallium Nine it is grey. Here is list of configuration where it works as expected (expected = how it works on native Windows): Windows 7 + D3D9 + AMD graphics Windows 7 + D3D9 + Intel graphics Linux + Wine + Gallium Nine + AMD graphics (Mesa) Here is list of configuration where it does not work (renders black objects): Windows 7 + WineD3D + AMD graphics Windows 7 + WineD3D + Intel graphics Linux + Wine + WineD3D + AMD graphics (Mesa) Linux + Wine + WineD3D + Intel graphics (Mesa) There are possibly two issues in attached pixel shader: 1) uninitialized IN.lightVec 2) usage of normalize() function (and possible division by zero) But here is the strange behaviour: 1) when I set IN.lightVec red, green or blue to 0.0 (one or two of them, but not all of them, because it cause crash), then it is rendered black in Windows and in Wine as well. 2) when I set IN.lightVec.r (for example) to "IN.lightVec.r + 0.0f", then it has no effect. >From point 2 it looks like IN.lightVec default values are 0.0f, but from point 1 it looks opposite. So I have no idea what are values of uninitialized vector. I thought that it could be related to bug #34266 [1], but: 1) created patch did not work for me 2) when I set IN.lightVec to zero, the bug disappears I can upload simple d3d app which use these effect and also binary file (exe). I have no D3D (and D3D shaders) deep knowledge, so maybe I something understand wrong. I also used native d3dcompiler_43 so Wine could compile these shaders. [1] https://bugs.winehq.org/show_bug.cgi?id=34266 -- 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.

Oct. 31, 2017

[Bug 43947] Disk size in Wine is not correct

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=43947 --- Comment #1 from Christoph Heilmann <christoph.heilmann(a)gmx.de> --- The disk drive is a Samsung ssd: Oct 29 13:49:09 kernel: [ 7.576322] scsi host0: ahci Oct 29 13:49:09 kernel: [ 7.576424] scsi host1: ahci Oct 29 13:49:09 kernel: [ 7.576532] scsi host2: ahci Oct 29 13:49:09 kernel: [ 7.576627] scsi host3: ahci Oct 29 13:49:09 kernel: [ 7.576729] scsi host4: ahci Oct 29 13:49:09 kernel: [ 7.576817] scsi host5: ahci Oct 29 13:49:09 kernel: [ 7.576854] ata1: SATA max UDMA/133 abar m2048(a)0xc7332000 port 0xc7332100 irq 32 Oct 29 13:49:09 kernel: [ 7.576859] ata2: SATA max UDMA/133 abar m2048(a)0xc7332000 port 0xc7332180 irq 32 Oct 29 13:49:09 kernel: [ 7.576863] ata3: SATA max UDMA/133 abar m2048(a)0xc7332000 port 0xc7332200 irq 32 Oct 29 13:49:09 kernel: [ 7.576868] ata4: SATA max UDMA/133 abar m2048(a)0xc7332000 port 0xc7332280 irq 32 Oct 29 13:49:09 kernel: [ 7.576872] ata5: SATA max UDMA/133 abar m2048(a)0xc7332000 port 0xc7332300 irq 32 Oct 29 13:49:09 kernel: [ 7.576877] ata6: SATA max UDMA/133 abar m2048(a)0xc7332000 port 0xc7332380 irq 32 Oct 29 13:49:09 kernel: [ 7.890224] ata6: SATA link down (SStatus 0 SControl 300) Oct 29 13:49:09 kernel: [ 7.890523] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Oct 29 13:49:09 kernel: [ 7.890862] ata5: SATA link down (SStatus 0 SControl 300) Oct 29 13:49:09 kernel: [ 7.891002] ata4: SATA link down (SStatus 0 SControl 300) Oct 29 13:49:09 kernel: [ 7.891095] ata3: SATA link down (SStatus 0 SControl 300) Oct 29 13:49:09 kernel: [ 7.891167] ata2: SATA link down (SStatus 0 SControl 300) Oct 29 13:49:09 kernel: [ 7.892453] ata1.00: supports DRM functions and may not be fully accessible Oct 29 13:49:09 kernel: [ 7.892858] ata1.00: NCQ Send/Recv Log not supported Oct 29 13:49:09 kernel: [ 7.892859] ata1.00: ATA-9: Samsung SSD 840 EVO 500GB, EXT0CB6Q, max UDMA/133 Oct 29 13:49:09 kernel: [ 7.892860] ata1.00: 976773168 sectors, multi 1: LBA48 NCQ (depth 31/32), AA Oct 29 13:49:09 kernel: [ 7.893052] ata1.00: supports DRM functions and may not be fully accessible Oct 29 13:49:09 kernel: [ 7.893427] ata1.00: NCQ Send/Recv Log not supported Oct 29 13:49:09 kernel: [ 7.893428] ata1.00: configured for UDMA/133 Oct 29 13:49:09 kernel: [ 7.893766] scsi 0:0:0:0: Direct-Access ATA Samsung SSD 840 CB6Q PQ: 0 ANSI: 5 Oct 29 13:49:09 m4348 kernel: [ 7.908432] dca service started, version 1.12.1 -- 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.

Oct. 31, 2017

[Bug 42284] Enable using Wine with Wayland and without X on Linux

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=42284 Luke Bratch <luke(a)bratch.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |luke(a)bratch.co.uk -- 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.

Oct. 31, 2017

[Bug 43944] msi/action tests fail on armv7l

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=43944 --- Comment #1 from Hans Leidekker <hans(a)meelstraat.net> --- Can you attach a +msi trace? -- 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.

Oct. 31, 2017