June 2018 - Wine-Bugs - list.winehq.org

[Bug 45345] Unity Game Lines Infinite shows a blank screen

by wine-bugs＠winehq.org

June 17, 2018

[Bug 45345] The game runs and you can hear the sound but it shows a blank screen.

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=45345 Fabian Maurer <dark.shadow4(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4(a)web.de --- Comment #2 from Fabian Maurer <dark.shadow4(a)web.de> --- FWIW, this game has a native Linux version - if you just want to play. -- 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.

June 17, 2018

[Bug 45345] The game runs and you can hear the sound but it shows a blank screen.

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=45345 --- Comment #1 from mrrmx <alexterranova81(a)gmail.com> --- https://store.steampowered.com/app/733050/Lines_Infinite/ (It's a Unity Game) *SHOWS BLANK SCREEN -- 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.

June 17, 2018

[Bug 45345] New: The game runs and you can hear the sound but it shows a blank screen.

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=45345 Bug ID: 45345 Summary: The game runs and you can hear the sound but it shows a blank screen. Product: Wine Version: 3.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: alexterranova81(a)gmail.com Distribution: --- Created attachment 61633 --> https://bugs.winehq.org/attachment.cgi?id=61633 Console Logs OS: Linux Mint 18.3 x64 KDE/ Wine 3.10 / Using recommended Graphics Drivers CPU: AMD VideoCard: GeForce GTX 750 RAM: 8GB The game runs with sound, but you get a blank screen https://www.pastiebin.com/5b269712b01a0 -- 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.

June 17, 2018

[Bug 45335] Morita i-Dixel CT imaging software 'OneVolumeViewer' crashes when opening volume files (broken application, working directory must be short path)

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=45335 --- Comment #11 from Fabian Maurer <dark.shadow4(a)web.de> --- FWIW, I asked someone on #winehackers to test with proprietary drivers, and this is the result: http://paste.debian.net/1029572/. So it's definitely not the driver that's wrong here. I wasn't sure, since proprietary drivers sometimes just hide faulty behavior and it seems to work. Also, I tested on my VM again, and I must admit I screwed up the test. The VM has had only a tiny amount of RAM, and the program simply ran out of memory. Now that I have it 4GB, the program runs flawless, even with a crazy long path. There seems to be some issue on wine that runs deeper. -- 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.

June 17, 2018

[Bug 45335] Morita i-Dixel CT imaging software 'OneVolumeViewer' crashes when opening volume files (broken application, working directory must be short path)

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=45335 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEW --- Comment #10 from Anastasius Focht <focht(a)gmx.net> --- Hello folks, --- quote --- So is the path issue still relevant or what does this mean? --- quote --- hard to tell. Although the internal debug/dev setting works around the true cause should be found as this works out of the box on Windows without any registry tweaks (OP didn't specify which path he used). Since you've tested this earlier on some Windows VM: --- quote --- Does it work when you download it and run it on a windows machine? It doesn't work on my VM, at least - gives me a Runtime-Error. --- quote --- Could you try to put the app in some short path and re-check? Extract the .zip to 'C:\\onevolumeviewer' or another drive (rename/remove top-level directory 'Andriy Pavlovych Kniazyuk_20180115171449.SL'). The working path length problem already makes me think there are multiple separate bugs present. Maybe there is a cascading-type bug where a partial/improper initialization of app data results in more issues that are normally hidden. With the initial opengl crash I've managed to get something usable by debugging with native (winedbg backtrace is not usable, stack/frame corruption). --- snip --- Wine-gdb> bt #0 osmesa_st_framebuffer_flush_front (stctx=0x7bd8b350, stfbi=0x7bd92720, statt=ST_ATTACHMENT_FRONT_LEFT) at osmesa.c:311 #1 0x7a2b1763 in st_manager_flush_frontbuffer (st=0x7bd8b350) at state_tracker/st_manager.c:1097 #2 0x7a28092c in st_glFinish (ctx=0x7aa66750) at state_tracker/st_cb_flush.c:106 #3 0x7a0c6c34 in _mesa_Finish () at main/context.c:1863 #4 0x7a8b10ab in glFinish () at /home/focht/projects/wine/mainline-src/dlls/opengl32/opengl_norm.c:638 #5 0x10052513 in ?? () #6 0x1004f90b in ?? () #7 0x1007b4ec in ?? () #8 0xff6af8e4 in ?? () #9 0x00000000 in ?? () Wine-gdb> si 0x7a516c6d in osmesa_st_framebuffer_flush_front (stctx=0x7bd8b350, stfbi=0x7bd92720, statt=ST_ATTACHMENT_FRONT_LEFT) at osmesa.c:345 345 in osmesa.c Wine-gdb> si 0x7a516d2a 368 in osmesa.c Wine-gdb> si memcpy (__len=4, __src=0x67177280, __dest=0x2600000) at /usr/include/bits/string_fortified.h:34 warning: Source file is more recent than executable. 34 return __builtin___memcpy_chk (__dest, __src, __len, __bos0 (__dest)); --- snip --- Essentially the user provided image buffer memory (0x2600000) is no longer valid here. The app has multiple threads that do GL calls. Each thread uses 'wglMakeCurrent' to bind its context to the mapped buffer(s) (represented by DIB). It seems there is a cross-thread passing of DIBs. One thread passes the pixel buffer from a DIB to some engine thread which in turn passes the buffer to GL using 'wglMakeCurrent'. It makes a rather long sequence of GL calls between 'wglMakeCurrent' and 'glFinish'. One of the threads re-creates DIBs while destroying old ones, leading to underlying pixel buffer of DIB being freed. At the point of 'glFinish' which ought to flush the front buffer, the mapped memory location is gone (DIB pixel buffer freed), causing 'memcpy' to page fault. Not sure yet where the problem is. There is also a skinning library 'XTPSkinManager' (Xtreme ToolkitPro) involved which hooks several API, including GDI32 ones. It could be another source of problems here. 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.

June 17, 2018

[Bug 45344] New: AcquireCredentialsHandle functions should be implemented inside sspicli

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=45344 Bug ID: 45344 Summary: AcquireCredentialsHandle functions should be implemented inside sspicli Product: Wine Version: 3.9 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: secur32 Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- Currently the AcquireCredentialsHandle functions are implemented inside secur32, and sspicli forwards them to secur32. However, when using native secur32, that results in a stack-overflow. Most likely on windows the functions are implemented in sspicli and secur32 forwards them. Most likely affects other functions, too. Application I tested it with (needs winXP): https://www.vavoo.tv/software/get?platform=win32&processor=i386&type=webins… -- 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.

June 17, 2018

[Bug 45343] Vavoo Webinstaller fails

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=45343 Fabian Maurer <dark.shadow4(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4(a)web.de Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #1 from Fabian Maurer <dark.shadow4(a)web.de> --- Confirming. You can set windows version to XP to bypass that error, but then it fails to download. -- 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.

June 17, 2018

[Bug 45343] Vavoo Webinstaller fails

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=45343 Maik Wagner <maiktapwagner(a)aol.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download, Installer CC| |maiktapwagner(a)aol.com Distribution|--- |SUSE URL| |https://www.vavoo.tv/softwa | |re/get?platform=win32&proce | |ssor=i386&type=webinstaller -- 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.

June 17, 2018

[Bug 45343] New: Vavoo Webinstaller fails

by wine-bugs＠winehq.org

https://bugs.winehq.org/show_bug.cgi?id=45343 Bug ID: 45343 Summary: Vavoo Webinstaller fails Product: Wine Version: 3.9 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: maiktapwagner(a)aol.com Distribution: --- Created attachment 61632 --> https://bugs.winehq.org/attachment.cgi?id=61632 Console Output wine 3.9 (staging) Hello everyone, Somebody in the German ubuntuusers.de forum had an issue of getting a software called "Vavoo" to run. I am getting the following (Windows) error message "Unable to run the Windows program wmic.exe to verify that Windows Update K2670838 is installed." Console output 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.

June 17, 2018