August 2018 - Wine-bugs - list.winehq.org

[Bug 17032] New: Lord of the Rings: Conquest gets stuck on main menu
by wine-bugs＠winehq.org 15 Sep '18

15 Sep '18

http://bugs.winehq.org/show_bug.cgi?id=17032 Summary: Lord of the Rings: Conquest gets stuck on main menu Product: Wine Version: 1.1.13 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P3 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: mcflow-forum(a)gmx.net Created an attachment (id=18831) --> (http://bugs.winehq.org/attachment.cgi?id=18831) command line output After creating a profile, the game enters the main menu. At the right you can choose multiplayer, singleplayer options and so on and on the upper middle part of the screen there is just a bar that says "loading". And it seems to load forever. I attached command line output but I am pretty sure there are no hints on it because the output does not change if the game changes from intro movies to main menu. Anyone any idea what component can be related to the problem? I tried WINEDEBUG=+all but then then wine is busy with giving output before something happens a very long time. -- 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.

1 9

[Bug 30518] New: 64-bit mono cannot run hello world
by wine-bugs＠winehq.org 15 Sep '18

15 Sep '18

http://bugs.winehq.org/show_bug.cgi?id=30518 Bug #: 30518 Summary: 64-bit mono cannot run hello world Product: Wine Version: 1.5.2 Platform: x86 OS/Version: Linux Status: NEW Keywords: download, source, testcase, win64 Severity: normal Priority: P2 Component: ntdll AssignedTo: wine-bugs(a)winehq.org ReportedBy: madewokherd(a)gmail.com Classification: Unclassified Created attachment 39919 --> http://bugs.winehq.org/attachment.cgi?id=39919 C# hello world source code To reproduce: * Download and extract http://madewokherd.nfshost.com/omgsecret/mono-64bit-exe.tar.gz, or build wine-mono from https://github.com/madewokherd/wine-mono, and copy mono.exe and libmono-2.0.dll from build-cross-x86_64/mono/mini/.libs to image/bin. * Download the attached helloworld.exe, or build it from helloworld.cs. * Run: wine image/bin/mono.exe helloworld.exe Currently, this results in wine: Call from 0x7fd2bcbde2fa to unimplemented function KERNEL32.dll.RtlInstallFunctionTableCallback, aborting -- 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.

1 16

[Bug 45246] New: Free Manga Downloader(all): no text on some boxes.
by wine-bugs＠winehq.org 14 Sep '18

14 Sep '18

https://bugs.winehq.org/show_bug.cgi?id=45246 Bug ID: 45246 Summary: Free Manga Downloader(all): no text on some boxes. Product: Wine Version: 3.6 Hardware: x86-64 URL: https://github.com/riderkick/FMD OS: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: luciojunior3(a)mail.com Distribution: Ubuntu Created attachment 61490 --> https://bugs.winehq.org/attachment.cgi?id=61490 Missing text. Same issue when running Manjaro, Nvidia 390 drivers. -- 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 24

[Bug 45735] New: Neo Manager (formerly known as Alphasmart Manager) not installed, cannot read out via USB
by wine-bugs＠winehq.org 14 Sep '18

14 Sep '18

https://bugs.winehq.org/show_bug.cgi?id=45735 Bug ID: 45735 Summary: Neo Manager (formerly known as Alphasmart Manager) not installed, cannot read out via USB Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: Stefaniee(a)gmx.de Distribution: --- Created attachment 62176 --> https://bugs.winehq.org/attachment.cgi?id=62176 backtrace of crashed installation The Neo Manager (or: Alphasmart Manager) is a software to read out/send to/manage files, which are written on the NEO device (a keyboard-like writing device). It is originally a software for windows (hence: wine used), the device is attached via usb. The installation using wine runs through until the last thing is "registering product" and then wine stops the installation giving me the back trace below. I tried it several times, no change. However, the program seems to be installed nevertheless and opens as it should. The problem: Although my device senses beeing attached to my laptop (it can be used as keyboard in any program as well, when not opened in the neo manager), the neo manager does not find any neo device. Vagely similar bugs are reported for windows users, if the used usb port is a usb hub. I tried on every usb port my laptop has, it doesn't recognize the device on either one. (I admit, I don't understand the usb port/usb hub difference... sorry.) -- 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 45738] New: Unable to compile on macOS after "winhttp: Use winsock sockets"
by wine-bugs＠winehq.org 14 Sep '18

14 Sep '18

https://bugs.winehq.org/show_bug.cgi?id=45738 Bug ID: 45738 Summary: Unable to compile on macOS after "winhttp: Use winsock sockets" Product: Wine Version: 3.14 Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: blocker Priority: P2 Component: winhttp Assignee: wine-bugs(a)winehq.org Reporter: gcenx83(a)gmail.com Before "winhttp: Use winsock sockets" ca56f992803420ef37d7a87158e572f981005e5d, it was possible to compile wine on macOS normally but now compiling fails. After reverting just the changes included in that commit I can compile the current head without 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.

1 8

[Bug 40064] New: Installing Atmel Studio & failed> issues with visual studio installtion and DDAConfigCA.exe
by wine-bugs＠winehq.org 14 Sep '18

14 Sep '18

https://bugs.winehq.org/show_bug.cgi?id=40064 Bug ID: 40064 Summary: Installing Atmel Studio & failed> issues with visual studio installtion and DDAConfigCA.exe Product: Wine Version: 1.8 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: hmf(a)inesctec.pt Distribution: --- Created attachment 53542 --> https://bugs.winehq.org/attachment.cgi?id=53542 DDAConfigCA.exe error log . env WINEARCH=win32 WINEPREFIX=~/.wine32atmel winecfg set it to windows 7 (NOT 8.1) . env WINEARCH=win32 WINEPREFIX=~/.wine32atmel winetricks -q corefonts mdac28 dotnet40 download gacutil-net40.tar.bz2 http://www.mediafire.com/download/v8rw5h1ra7maod4/gacutil-net40.tar.bz2 cp to /home/hmf/.cache/winetricks/dotnet40 rerun above note that reset the windows to thew XP version, change it again . env WINEARCH=win32 WINEPREFIX=~/.wine32atmel wine WinAVR-20100110-install.exe . env WINEARCH=win32 WINEPREFIX=~/.wine32atmel wine as-installer-7.0.634-full.exe Installation partially failed: An error occurred. Microsoft Visual Studio 2015 Shell (Isoltate) Close the window. No shortcut was added. reran the winecfg and this time did a modify - repair, which ended ok. Now we have a link env WINEPREFIX="/home/hmf/.wine32atmel" wine C:\\Program\ Files\\Atmel\\Studio\\7.0\\atmelstudio.exe Failed to run: err:eventlog:ReportEventW L"An unhandled win32 exception occurred in atmelstudio.exe [8]. Just-In-Time debugging this exception failed with the following error: 0x80004001\n\nCheck the documentation index for 'Just-in-time debugging, errors' for more information." During installation I get a error from DDAConfigCA.exe Added log. -- 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 40704] New: foobar2000 crashes on alt-F (file menu shortcut)
by wine-bugs＠winehq.org 14 Sep '18

14 Sep '18

https://bugs.winehq.org/show_bug.cgi?id=40704 Bug ID: 40704 Summary: foobar2000 crashes on alt-F (file menu shortcut) Product: Wine Version: 1.9.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: jimbo1qaz(a)gmail.com Distribution: --- Created attachment 54588 --> https://bugs.winehq.org/attachment.cgi?id=54588 foobar2000 crash handler log (alt-f) Not-really-duplicate of Bug 7205, reported in 2007 and closed in 2008. I'm using foobar2000 1.3.10. I first encountered this issue on Ubuntu 16.04 Cinnamon and Wine 1.6.2 x64, on a (I think) 32-bit wineprefix. # Setup * I also replicated this issue in Wine 1.9.10, 32-bit (PlayOnLinux). * To (hopefully) avoid foobar2000-specific tweaks, I used [Install dialog] -> _Install a non-listed program_. Then I created a new app profile and # Instructions * Install foobar2000 1.3.10. * Open foobar2000. Press [Alt-F]. # Results * foobar2000 crashes. The internal crash handler catches the crash and pops up a dialog. * I clicked "View Report" and saved a crash log. * Note that this bug is somewhat random. I've experienced GUI corruption, Wine crash handler, foobar2000 crash handler, or no issues at all. # Notes * [Alt-Enter] crashes. * [Alt] *focuses* the menu bar without crash. [Alt, Enter] opens the File menu without crash. * Afterwards, [Alt-F] etc. still crashes. * Clicking on any menu opens that menu without crash. * Afterwards, [Alt-F] etc. does NOT crash. * Clicking the "right-click menu" keyboard key opens an undo/redo menu. * This also prevents crashes. -- 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 30856] New: Atmel Studio 6 fails to start - Component missing
by wine-bugs＠winehq.org 14 Sep '18

14 Sep '18

http://bugs.winehq.org/show_bug.cgi?id=30856 Bug #: 30856 Summary: Atmel Studio 6 fails to start - Component missing Product: Wine Version: 1.5.5 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: onny(a)project-insanity.org Classification: Unclassified Created attachment 40414 --> http://bugs.winehq.org/attachment.cgi?id=40414 Debug logs of error message I've downloaded Atmel Studio 6 from here: http://www.mikrocontroller.net/articles/AVR-Studio and Microsoft Visual Studio 2010 Shell (Isolated) from here: https://www.microsoft.com/en-us/download/details.aspx?id=1366 After that, I ran: WINEARCH=win32 winetricks -q dotnet20 dotnet40 Because the setup of the IsolatedShell fails to extract, I manually extracted it using 7zip (alternatively WinRAR) and then ran the setup.exe. To avoid some error messages of the MS VSISOS setup, I copied some files: $ mkdir -p ~/.wine/drive_c/windows/Microsoft.NET/Framework/v2.0.50727/CONFIG $ cp /etc/mono/2.0/machine.config ~/.wine/drive_c/windows/Microsoft.NET/Framework/v2.0.50727/CONFIG/ $ mkdir ~/.wine/drive_c/windows/Microsoft.NET/Framework/v4.0.30319/config $ cp /etc/mono/4.0/machine.config ~/.wine/drive_c/windows/Microsoft.NET/Framework/v4.0.30319/config Now starting the Atmel Studio 6 setup works but still has some installation errors of single components, but nevertheless the installation succeeds. Starting the program fails with following error message: 0009:Call user32.MessageBoxW(00000000,0032d0c4 L"Cannot find one or more components. Please reinstall the application.",0032cea4 L"Microsoft Visual Studio Shell Isolated",00000010) ret=1001b67d Here is the complete +relay-Log (100mb+): http://onny.project-insanity.org/files/wine155-atmelstudio6-relay.txt In the attachment is a shorter log with only the MessageBox part and the errors before that. Hope that helps somehow, thanks! -- 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.

1 14

[Bug 38339] New: Steam: Can't change resolution in game
by wine-bugs＠winehq.org 14 Sep '18

14 Sep '18

https://bugs.winehq.org/show_bug.cgi?id=38339 Bug ID: 38339 Summary: Steam: Can't change resolution in game Product: Wine Version: 1.7.39 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: timsta2000(a)googlemail.com Distribution: --- Created attachment 51180 --> https://bugs.winehq.org/attachment.cgi?id=51180 Terminal output. Don't know if this is all, but I think it is. I've installed Call of Duty 4 Modern Warfare over Steam, but the resolution, when I start the game, drops to 640*480( with a screen with 1600*900 ). The rest of the screen is black. When I try to set a new resolution the game just crashes and the resoluton is still 640*480 in Unity. -- 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 45430] New: Improve diagnostics of 'D3DxxCreateDevice' failures for warp driver type ( D3D10_DRIVER_TYPE_WARP or D3D_DRIVER_TYPE_WARP)
by wine-bugs＠winehq.org 14 Sep '18

14 Sep '18

https://bugs.winehq.org/show_bug.cgi?id=45430 Bug ID: 45430 Summary: Improve diagnostics of 'D3DxxCreateDevice' failures for warp driver type (D3D10_DRIVER_TYPE_WARP or D3D_DRIVER_TYPE_WARP) Product: Wine Version: 3.11 Hardware: x86-64 OS: Linux Status: NEW Severity: enhancement Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, for improving diagnostics of unsupported drivers with 'D3DxxCreateDevice'. While trying out some games which support the DX11 Warp software renderer on Windows platforms (https://docs.microsoft.com/en-us/windows/desktop/direct3darticles/directx-w…) using command line, the output was not super useful. In fact it's a bit inconsistent. 'D3D10CreateDevice1' -> handles 'D3D10_DRIVER_TYPE_WARP' explicitly in fixme trace https://source.winehq.org/git/wine.git/blob/HEAD:/dlls/d3d10_1/d3d10_1_main… 'D3D11CreateDevice' -> default (error) case, only enum value printed https://source.winehq.org/git/wine.git/blob/HEAD:/dlls/d3d11/d3d11_main.c#l… 'D3D10CreateDevice' -> default (error) case, only enum value printed https://source.winehq.org/git/wine.git/blob/HEAD:/dlls/d3d10/d3d10_main.c#l… --- snip --- ... 0030:Ret ucrtbase.memcpy() retval=0022ea88 ret=140e19601 0030:Call d3d11.D3D11CreateDeviceAndSwapChain(00000000,00000005,00000000,00000000,0022f3d8,00000003,00000007,0022f3f0,2127fb38,2127fb30,2127fb40,0022f3d0) ret=140b91f80 0030:Call dxgi.CreateDXGIFactory1(7f270d9df180,0022edf0) ret=7f270d975d1e 0030:trace:dxgi:CreateDXGIFactory1 iid {7b7166ec-21c7-44ae-b21a-c9ae321ae369}, factory 0x22edf0. ... 0030:trace:d3d:wined3d_create Created wined3d object 0xc6c620. 0030:Ret wined3d.wined3d_create() retval=00c6c620 ret=7f270d905c55 0030:Call wined3d.wined3d_mutex_unlock() ret=7f270d905c74 0030:Ret wined3d.wined3d_mutex_unlock() retval=00000000 ret=7f270d905c74 0030:trace:dxgi:dxgi_factory_create Created factory 0xc6c5d0. 0030:trace:dxgi:dxgi_factory_QueryInterface iface 0xc6c5d0, iid {7b7166ec-21c7-44ae-b21a-c9ae321ae369}, out 0x22edf0. 0030:trace:dxgi:dxgi_factory_AddRef 0xc6c5d0 increasing refcount to 2. 0030:trace:dxgi:dxgi_factory_Release 0xc6c5d0 decreasing refcount to 1. 0030:Ret dxgi.CreateDXGIFactory1() retval=00000000 ret=7f270d975d1e 0030:fixme:d3d11:D3D11CreateDevice Unhandled driver type 0x5. ... 0030:Ret d3d11.D3D11CreateDeviceAndSwapChain() retval=80004005 ret=140b91f80 ... --- snip --- It later crashes, likely due to missing WARP driver support. Having the unhandled WARP driver type explicitly "stringified" could improve the situation of diagnosing end user problems. I actually had to look up the enum value. Might be a bit off-topic to this ticket: Is Direct3D 11 WARP driver support ever considered in Wine? I guess getting DX11+ feature support with hardware drivers to work perfectly (tm) is much higher priority. The MS website (https://docs.microsoft.com/en-us/windows/desktop/direct3darticles/directx-w…) lists some interesting use-cases though. 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.

1 5