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

[Bug 38467] New: Win86Emu doesn't run (Loadlibrary flag missing)
by wine-bugs＠winehq.org April 20, 2020

April 20, 2020

https://bugs.winehq.org/show_bug.cgi?id=38467 Bug ID: 38467 Summary: Win86Emu doesn't run (Loadlibrary flag missing) Product: Wine Version: unspecified Hardware: arm OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mmediouni(a)gmx.fr Distribution: --- fixme:module:load_library unsupported flag(s) used (flags: 0x00000060) "Can't reserve memory file(file too big or invalid format" error is shown. (follow-up to Bug33997) -- 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 16

[Bug 42790] New: Error in "Pilot Brothers" game: Unhandled exception: divide by zero in 32-bit code (0x00401096).
by wine-bugs＠winehq.org April 20, 2020

April 20, 2020

https://bugs.winehq.org/show_bug.cgi?id=42790 Bug ID: 42790 Summary: Error in "Pilot Brothers" game: Unhandled exception: divide by zero in 32-bit code (0x00401096). Product: Wine Version: 1.6.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: aleksanders(a)yandex.ru Distribution: --- Created attachment 57817 --> https://bugs.winehq.org/attachment.cgi?id=57817 Backtrace file here Unable to start game - error after pressing "Start" button. -- 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 45369] New: Under certain (unknown) conditions, winedbg.exe continually spawns explorer.exe sub-processes until it is killed
by wine-bugs＠winehq.org April 20, 2020

April 20, 2020

https://bugs.winehq.org/show_bug.cgi?id=45369 Bug ID: 45369 Summary: Under certain (unknown) conditions, winedbg.exe continually spawns explorer.exe sub-processes until it is killed Product: Wine-staging Version: 3.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: roman(a)hargrave.info CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 61679 --> https://bugs.winehq.org/attachment.cgi?id=61679 A portion of wine console output collected after the event I'd like to open with a note that I am not submitting this on wine-devel, as I the only application that has been able to cause these crashes will not run well enough to reliably reproduce the error without DXVK, and in turn wine-staging (as far as I am aware, DXVK continues to require a patch in the staging patchset that has not been mainlined - correct me if i am wrong). The application which has been causing problems is Grand Theft Auto V, though specifically Rock Star Social Club (I can't be terribly certain - but the issue tends to crop up when social club is brought in to the question). Glancing at the crash info in the terminal (winedbg is actually not even visible yet as it is too preoccupied with explorer), this is the result of an exception thrown within libcef.dll, which judging by the name and the platform which it is used by, is chromium embedded framework - a common offender. Knowing this, i'll just avoid the social club in-game if at all possible, but what's concerning is the outcome. Something about the manner in which it has gone about crashing causes some _very_ eratic behaviour in winedbg. For some reason, `explorer.exe /desktop` is invoked as a child process of winedbg and then fails to start. Another instance of explorer with the same parameters is then started by the child, as well as some concurrent instances (I think - when you have so many process running that your PIDs roll over it start to get hard to track who started who) - effectively an explorer fork bomb, though it dies off fast enough if you get to winedbg and kill it or its parent. -- 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 26

[Bug 48963] New: wineusb.sys: Include file of libusb is named usb.h on Ubuntu 18.04 LTS
by WineHQ Bugzilla April 20, 2020

April 20, 2020

https://bugs.winehq.org/show_bug.cgi?id=48963 Bug ID: 48963 Summary: wineusb.sys: Include file of libusb is named usb.h on Ubuntu 18.04 LTS Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ulrich.gemkow(a)ikr.uni-stuttgart.de Distribution: --- Maybe it is too early for this report, then please apologize and ignore: The new wineusb.sys assumes that the name of the libusb header file is libusb.h. At least on Ubuntu 18.04 the include file is named usb.h. (see https://packages.ubuntu.com/bionic/i386/libusb-dev/filelist) -- 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 29708] New: Wine processes take ages to start on Solaris
by wine-bugs＠winehq.org April 20, 2020

April 20, 2020

http://bugs.winehq.org/show_bug.cgi?id=29708 Bug #: 29708 Summary: Wine processes take ages to start on Solaris Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: fgouget(a)codeweavers.com Classification: Unclassified Winetest takes ages to complete on Solaris, particularly on Solaris 10: about 80 minutes. I instrumented winetest to trace the time it takes to run each test and the result is eloquent: starting a Wine process takes 4 to 5 seconds on Solaris 10. With some grepping of the logs I built the following table which shows this issue. Note that all operating systems are running inside VMware on the same machine (one at a time of course), so they should all have the same performance. Seconds freebsd81 solaris1111 solaris10u9 0 401 169 0 1 48 220 0 2 8 43 0 3 10 16 15 4 2 6 123 5 4 2 190 6 2 3 45 7 3 4 21 8 3 2 9 9 2 1 8 10-29 17 24 34 30-59 3 4 8 60-99 1 1 3 100-119 0 0 1 120- 1 8 9 Also note that this is not the first-process start delay since winetest.exe is already running. I took a trace with +timestamp but it only showed the last 0.6 seconds of execution so more digging is needed. -- 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.

2 9

[Bug 48634] New: Fallout New Vegas unreliable mouse\cursor, can't move or player can't turn the camera around.
by WineHQ Bugzilla April 20, 2020

April 20, 2020

https://bugs.winehq.org/show_bug.cgi?id=48634 Bug ID: 48634 Summary: Fallout New Vegas unreliable mouse\cursor, can't move or player can't turn the camera around. Product: Wine-staging Version: 5.2 Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: avenjames(a)live.com CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com I got Fallout: New Vegas setup from GOG and found that there's a critical problem to play this game, While I launch and get reach to the main menu, the mouse (we said cursor) was just stucking there but can very hard to move, I have to move the mouse fast and quick then the cursor just moving a bit. I'd googled that saying the solution: 1. change the value bBackground Mouse = 0 to = 1 which within ini files. 2. remove the 360 controller within the game setting and the ini files. 3. reboot machine or reinstalling the game. it's funny that even I'd tried these ways and the cursor finally moving as what the mouse going but after starting the new game and then I can't control the player's camera, it just stuck again and couldn't turn the cam around, the funny thing is the cursor is working very normal in menu\pipboy interface at this moment. once I switch the window via alt+tab, the problem of the mouse come back again then the player camera could hardly turn this time!! even all these ways I'd been through but didn't make it working as what it should be eventually. I don't think this problem related to Wine but it might be a bug that related to the Joysticks device control because I googled that people always said it should be the Joysticks problem to make it like. -- 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 36088] New: mansion88 poker
by wine-bugs＠winehq.org April 20, 2020

April 20, 2020

http://bugs.winehq.org/show_bug.cgi?id=36088 Bug ID: 36088 Summary: mansion88 poker Product: WineHQ Apps Database Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: appdb-unknown Assignee: wine-bugs(a)winehq.org Reporter: andrhi2ean(a)gmail.com Created attachment 48274 --> http://bugs.winehq.org/attachment.cgi?id=48274 mansion88 poker doesnt work on my pc program doesnt work -- 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 38211] New: Skyrim: freezes on opening screen
by wine-bugs＠winehq.org April 20, 2020

April 20, 2020

https://bugs.winehq.org/show_bug.cgi?id=38211 Bug ID: 38211 Summary: Skyrim: freezes on opening screen Product: Wine Version: 1.6.2 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: angeltroubler(a)gmail.com Created attachment 51004 --> https://bugs.winehq.org/attachment.cgi?id=51004 output for Program Error Details When opening Skyrim through Steam, which is running through Wine, I get a Program Error saying "The program Setup.exe has encountered a serious problem and needs to close." The details for this are attached below. If I close this window, the game opens the initial play window, but after clicking play, it shows the Bethesda logo and then freezes on the Skyrim logo. If I then switch applications and return, the Play/Load/Credits/Quit buttons show up, but are missing letters and don't appear to have loaded correctly. Clicking play or loading a save results in a complete freeze. Any ideas on how I might be able to fix this? Thanks so much. -- 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 11

[Bug 42041] New: Origin Setup and Origin Thin Setup installation fails immediately
by wine-bugs＠winehq.org April 20, 2020

April 20, 2020

https://bugs.winehq.org/show_bug.cgi?id=42041 Bug ID: 42041 Summary: Origin Setup and Origin Thin Setup installation fails immediately Product: Wine Version: 2.0-rc2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alexchandel(a)gmail.com Distribution: --- Attempting to install both the OriginSetup.exe and OriginThinSetup.exe on 32-bit wine-2.0-rc2 yields the same garbage error (pasted because it's so short): fixme:ver:GetCurrentPackageId (0x33e9dc 0x0): stub fixme:file:FindFirstFileExW flags not implemented 0x00000002 err:wintab32:LoadTablet LoadTabletInfo(0x10050) failed fixme:system:SetProcessDPIAware stub! fixme:win:EnumDisplayDevicesW ((null),0,0x33f178,0x00000000), stub! fixme:win:EnumDisplayDevicesW ((null),0,0x33f318,0x00000000), stub! fixme:dxgi:dxgi_check_feature_level_support Ignoring adapter type. fixme:winediag:dxgi_check_feature_level_support None of the requested D3D feature levels is supported on this GPU with the current shader backend. fixme:win:EnumDisplayDevicesW ((null),0,0x33f318,0x00000000), stub! fixme:dxgi:dxgi_check_feature_level_support Ignoring adapter type. fixme:winediag:dxgi_check_feature_level_support None of the requested D3D feature levels is supported on this GPU with the current shader backend. fixme:win:EnumDisplayDevicesW ((null),0,0x33f438,0x00000000), stub! fixme:wgl:get_dc_pixel_format DC for window 0x5005e of other process: not implemented fixme:wgl:set_pixel_format DC for window 0x5005e of other process: not implemented err:d3d:context_create Failed to set pixel format 29 on device context 0x15004b. fixme:wgl:get_dc_pixel_format DC for window 0x5005e of other process: not implemented fixme:wgl:set_pixel_format DC for window 0x5005e of other process: not implemented err:d3d:context_create Failed to set pixel format 29 on device context 0x15004b. fixme:wgl:get_dc_pixel_format DC for window 0x5005e of other process: not implemented fixme:wgl:set_pixel_format DC for window 0x5005e of other process: not implemented err:d3d:context_create Failed to set pixel format 29 on device context 0x15004b. fixme:wgl:get_dc_pixel_format DC for window 0x5005e of other process: not implemented fixme:wgl:set_pixel_format DC for window 0x5005e of other process: not implemented err:d3d:context_create Failed to set pixel format 29 on device context 0x15004b. fixme:wgl:get_dc_pixel_format DC for window 0x5005e of other process: not implemented fixme:wgl:set_pixel_format DC for window 0x5005e of other process: not implemented err:d3d:context_create Failed to set pixel format 29 on device context 0x15004b. fixme:wgl:get_dc_pixel_format DC for window 0x5005e of other process: not implemented fixme:wgl:set_pixel_format DC for window 0x5005e of other process: not implemented err:d3d:context_create Failed to set pixel format 29 on device context 0x15004b. fixme:wgl:get_dc_pixel_format DC for window 0x5005e of other process: not implemented fixme:wgl:set_pixel_format DC for window 0x5005e of other process: not implemented err:d3d:context_create Failed to set pixel format 29 on device context 0x15004b. fixme:wgl:get_dc_pixel_format DC for window 0x5005e of other process: not implemented fixme:wgl:set_pixel_format DC for window 0x5005e of other process: not implemented err:d3d:context_create Failed to set pixel format 29 on device context 0x15004b. fixme:wgl:get_dc_pixel_format DC for window 0x5005e of other process: not implemented fixme:wgl:set_pixel_format DC for window 0x5005e of other process: not implemented err:d3d:context_create Failed to set pixel format 29 on device context 0x15004b. fixme:wgl:get_dc_pixel_format DC for window 0x5005e of other process: not implemented fixme:wgl:set_pixel_format DC for window 0x5005e of other process: not implemented err:d3d:context_create Failed to set pixel format 29 on device context 0x15004b. fixme:msvcrt:__clean_type_info_names_internal (0x5204014) stub fixme:ver:GetCurrentPackageId (0x33f398 0x0): stub fixme:ver:GetCurrentPackageId (0x33f5a4 0x0): stub err:ole:CoInitializeEx Attempt to change threading model of this apartment from apartment threaded to multi-threaded fixme:ole:CoInitializeSecurity (0x0,-1,0x0,0x0,0,3,0x0,0,0x0) - stub! fixme:wbemprox:client_security_SetBlanket 0x49a5b960, 0x216bd8, 10, 0, (null), 3, 3, 0x0, 0x00000000 fixme:wbemprox:client_security_Release 0x49a5b960 fixme:mountmgr:harddisk_ioctl The DISK_PARTITION_INFO and DISK_DETECTION_INFO structures will not be filled fixme:mountmgr:harddisk_ioctl The DISK_PARTITION_INFO and DISK_DETECTION_INFO structures will not be filled fixme:win:EnumDisplayDevicesW ((null),0,0x33e998,0x00000000), stub! fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x33ef68 1 C) semi-stub fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x33edb8 1 C) semi-stub fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x33ef28 1 C) semi-stub fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0x33ef58 1 C) semi-stub err:ole:CoInitializeEx Attempt to change threading model of this apartment from apartment threaded to multi-threaded fixme:netprofm:connection_point_Advise 0x218018, 0x4b5f4dc, 0x4b5f544 - stub fixme:netprofm:list_manager_GetConnectivity 0x5970a58, 0x33fb34 fixme:winsock:set_dont_fragment IP_DONTFRAGMENT for IPv4 not supported in this platform fixme:winhttp:WinHttpDetectAutoProxyConfigUrl discovery via DHCP not supported fixme:toolhelp:CreateToolhelp32Snapshot Unimplemented: heap list snapshot fixme:toolhelp:Heap32ListFirst : stub fixme:font:RemoveFontMemResourceEx (0x82f24eb1) stub fixme:font:RemoveFontMemResourceEx (0x82ffce79) stub fixme:font:RemoveFontMemResourceEx (0x82f88db1) stub fixme:font:RemoveFontMemResourceEx (0x82c47429) stub fixme:font:RemoveFontMemResourceEx (0x82c13be1) stub fixme:font:RemoveFontMemResourceEx (0x82c2fb49) stub fixme:font:RemoveFontMemResourceEx (0x82ce5ef1) stub fixme:font:RemoveFontMemResourceEx (0x81504311) stub fixme:font:RemoveFontMemResourceEx (0x815d1269) stub fixme:font:RemoveFontMemResourceEx (0x815ef099) stub fixme:font:RemoveFontMemResourceEx (0x81f25301) stub fixme:font:RemoveFontMemResourceEx (0x81858301) stub fixme:thread:SetThreadIdealProcessor (0x20c): stub I couldn't say why it fails, but errors include "err:wintab32:LoadTablet", "err:d3d:context_create", and "err:ole:CoInitializeEx". The machine has an Intel HD Graphics 4000 graphics card, which was added to wine in bug #39796. Note these errors appear different from bug #41410 -- 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 15

[Bug 41272] New: Origin Crash after Login
by wine-bugs＠winehq.org April 20, 2020

April 20, 2020

https://bugs.winehq.org/show_bug.cgi?id=41272 Bug ID: 41272 Summary: Origin Crash after Login Product: Wine Version: 1.9.16 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msvcp Assignee: wine-bugs(a)winehq.org Reporter: qops1981(a)gmail.com Distribution: --- Created attachment 55572 --> https://bugs.winehq.org/attachment.cgi?id=55572 Origin Debug Log After installing Origin using file from this link: https://download.dm.origin.com/origin/live/OriginSetup.exe I get the login Screen. At this point all seems well. I enter my credentials and submit. The system hangs for a min then I get the Crash report from the Origin Applications. I have experienced this problem over multiple versions of wine and through two versions of Fedora ( 23 & 24 ). I have also done multiple installs of the OS & wine so there were many fresh installs to work from. Attached should be the Wine Debug Log & the Crash report from Origin. Thank You -Bill -- 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 18