July 2020 - Wine-Bugs - list.winehq.org

[Bug 49631] Wine does not fill in Vulkan device LUID property when running in Virtual Desktop

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=49631 --- Comment #7 from Alexandr Oleynikov <sashok.olen(a)gmail.com> --- The patch works, thanks! -- 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.

July 31, 2020

[Bug 49644] wine 5.13 devel loops trying to launch first win app then ends doing nothing ubuntu 16.04

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=49644 Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |o.dierick(a)piezo-forte.be --- Comment #1 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- Hello, Does the command 'wine notepad' launch notepad? Which office installer is it? https://appdb.winehq.org/objectManager.php?sClass=application&iId=31 Please attach a normal (=without WINEDEBUG) terminal output. Instructions to get a log can be found there: https://wiki.winehq.org/FAQ#get_log Regards. -- 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.

July 31, 2020

[Bug 19775] Largo Winch: crash with hardware vertex shader

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=19775 Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED CC| |o.dierick(a)piezo-forte.be Status|NEW |RESOLVED --- Comment #11 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- Hello, Reported fixed, resolving. Regards -- 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.

July 31, 2020

[Bug 47731] World of Warcraft BFA Crash with error 132 Memory could not be read.

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=47731 --- Comment #31 from Lunia <LittleLunia94(a)Gmail.com> --- (In reply to Sveinar Søpler from comment #30) > (In reply to Lunia from comment #29) > > Currently have this happen constantly on lutris-5.7.5 with DXVK 1.7. > > > > It mostly happens when I take any portal, it will crash on the loading > > screen and from there on the game will constantly crash more and more often > > until I delete the GLCache and WoW Cache folders. > > > > From there on it'll be fine again for a while until the next crash occurs > > and it snowballs into more and more crashes again and I have to delete the > > folders again. > > What driver are you using? > > The 450.56.02 driver from https://developer.nvidia.com/vulkan-driver seems > to be working quite well with vkd3d-proton and d3d12 atleast. > > Depending on distro, it can be a slightly scary business to upgrade the > driver using the nVidia .run version vs. distro package. In the case of > deb/ubuntu the "official" repo is horribly far behind on the releases me > thinks. I'm using 450.57 right now. DX12 with VKD3D works perfectly fine with no error 132 except sometimes when closing the game, however DX12 VKD3D performance is quite a lot worse than DX11 DXVK for me, so I'd love to get DXVK working. :( This seems to be some weird issue with DXVK + NVIDIA. Doitsujin said it was fixed by NVIDIA in like 440.59 but clearly that hasn't really been the case. My friend using an AMD GPU has no issue whatsoever and whenever I google this problem every single person seems to have an NVIDIA GPU. -- 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.

July 31, 2020

[Bug 49597] Guitar Pro 7.5 can't open valid .gp files once they have been changed in any way (like composing), also cannot open newly created .gp files

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=49597 joaopa <jeremielapuree(a)yahoo.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree(a)yahoo.fr --- Comment #3 from joaopa <jeremielapuree(a)yahoo.fr> --- Explain how to add a new note or a notation. I did not find how to do. to collect a console output: in a terminal cd ~/.wine/drive_c/Program Files/Arobas Music/Guitar Pro 7 wine GuitarPro7.exe&>~/log.txt and attach to this bug the file log.txt -- 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.

July 31, 2020

[Bug 19775] Largo Winch: crash with hardware vertex shader

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=19775 --- Comment #10 from joaopa <jeremielapuree(a)yahoo.fr> --- Still working fine with wine-5.13. Can an administrator close this bug as FIXED? -- 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.

July 31, 2020

[Bug 49645] New: Adobe Photoshop CC 2018 crashes at every "cancel" interaction

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=49645 Bug ID: 49645 Summary: Adobe Photoshop CC 2018 crashes at every "cancel" interaction Product: Wine-staging Version: 5.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: l4vebs1mx(a)relay.firefox.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 67846 --> https://bugs.winehq.org/attachment.cgi?id=67846 Backtrace Error Log I have been running Adobe Photoshop CC 2018 flawlessly from 5.10 onwards, but since staging 5.12 a usage breaking error appears: Whenever I cancel / close a dialogue by exiting it (via clicking cancel or esc), the bug occurs: Photoshop has presented an error dialogue "Could not complete your request" for every canceled interaction (example: using the crop tool and then using escape to not commiting the action). Since 5.12, this dialogue does not appear, instead the program crashes to Desktop. Any help would be much appreciated... Thank you all! -- 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.

July 31, 2020

[Bug 49644] New: wine 5.13 devel loops trying to launch first win app then ends doing nothing ubuntu 16.04

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=49644 Bug ID: 49644 Summary: wine 5.13 devel loops trying to launch first win app then ends doing nothing ubuntu 16.04 Product: Wine Version: 5.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: stevedonato(a)gmail.com Distribution: --- I just installed winehq-devel amd64 5.13~xenial on Linux Mint 18.3 (Ubuntu base 16.04). Just tried first win app (office install) wine program loader went into spinning circle for about 25 seconde did nothing and ended? Dell m4600 32GB Ram ssd drives Wine works perfect on my old release of linux mint 18.2 I think that one is wine 5.1 stable -- 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.

July 31, 2020

[Bug 49597] Guitar Pro 7.5 can't open valid .gp files once they have been changed in any way (like composing), also cannot open newly created .gp files

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=49597 --- Comment #2 from Davin Dittrich <narfkeks(a)yahoo.de> --- (In reply to Austin English from comment #1) > Please attach the terminal output. > > Did this work in previous application/wine versions? > > Is there a free demo/download available that shows this issue? I unfortunately don't know how to attach or even read the terminal output, so I cannot help you there. This link provides you with a trial version for 30 days, but I cannot say for sure that it has the same issue. It should, but I cannot guarantee it. https://www.guitar-pro.com/en/index.php?pg=download&software=gp7demo To create a file that does not work just open a new file and change anything in it, like adding a new note, working on the notations etc. you don't need any real knowledge on the program to do so. Just click into the notation, enter any number, safe the file, close the program and you got yourself a test subject. By now I could verify that the same bug appears on the system of a friend which has the same software config (Wine 5.12-1, Guitar Pro 7.5.4 Build 1799). Also, sorry for the very late reply -- 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.

July 31, 2020

[Bug 49643] New: Calling ClipCursor too frequently can cause stack overflow in foreground window thread.

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=49643 Bug ID: 49643 Summary: Calling ClipCursor too frequently can cause stack overflow in foreground window thread. Product: Wine Version: 5.13 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: rbernon(a)codeweavers.com Distribution: --- Created attachment 67845 --> https://bugs.winehq.org/attachment.cgi?id=67845 Reproducing sample application Calling ClipCursor too frequently in a non-foreground thread may cause the foreground window thread to overflow its stack. This is happening under some circumstances with CoD: WWII. This is inherent to the current implementation where every ClipCursor request from a non-foreground thread involves synchronously sending internal messages to the foreground window thread, then to the desktop thread. Each ClipCursor request is processed when the desktop thread is notified, growing the stack every time, until it overflows. The attached program can be used to easily reproduce the issue. -- 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.

July 31, 2020