January 2021 - Wine-bugs - list.winehq.org

[Bug 39512] New: Make it possible to run multiple tests in a single task
by wine-bugs＠winehq.org 12 Feb '21

12 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=39512 Bug ID: 39512 Summary: Make it possible to run multiple tests in a single task Product: Wine-Testbot Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- Currently when a patch touches multiple tests the TestBot creates one task per test per VM, and even multiple jobs if the patch touches tests for multiple dlls. For instance currently Wine patches are tested on four 32 bit VMs and five 64 bit VMs. So a patch that modified 2 tests in one dll and 3 in another would create 2 jobs and 72 tasks (2 build tasks, (2+3)*(4+5) 32 bit tasks, and (2+3)*5 64 bit tasks). The overall run time would obviously be quite long, thus earning this type of (otherwise quite legitimate) patch the 'test bomb' nickname. The fix is to take the ability to build a WineTest executable with only a few tests (see bug 39065) further so that: * A WineTest executable containing only the modified tests is built. * The TestBot then creates only one job and one task per VM to run that test executable. * Just like in bug 39065 the tasks would have to specify a command line such that only the modified tests are run. That's not just for efficiency's sake but also to avoid getting test failures from unmodified tests. * Instead of having a constant 2 minutes timeout the tasks would also need to have a timeout that's in line with the number of tests to run. This could be something like: MIN(tests_count, 2) * 2 minutes + average_time * tests_count Where average_time would be some configurable constant (probably something around 3 to 5 seconds). -- 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 43809] New: Call of Duty WWII - PC Open Beta doesn't start
by wine-bugs＠winehq.org 12 Feb '21

12 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=43809 Bug ID: 43809 Summary: Call of Duty WWII - PC Open Beta doesn't start Product: Wine Version: 2.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: plata(a)mailbox.org Distribution: --- Wine 2.17 staging 64bit. After clicking "Run" in Steam, Steam says "is running" but nothing happens. Shortly after this, "is running" disappears again. There is no output in the Wine log at all. Some people seem to have the same issue on Windows as well so this *might* not be a problem of Wine after 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.

2 3

[Bug 43537] New: Radiofeed does not run
by wine-bugs＠winehq.org 12 Feb '21

12 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=43537 Bug ID: 43537 Summary: Radiofeed does not run Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: boz25(a)yahoo.com Distribution: --- Created attachment 58935 --> https://bugs.winehq.org/attachment.cgi?id=58935 I am new to this so I dont know what to put here. Program will not launch anymore. Happens a lot after updates. My Wine fonts look different now also. https://www.proscan.org/ -- 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 6

[Bug 45286] New: when running microsoft office 2010 or 2007 it crashes at opening time
by wine-bugs＠winehq.org 12 Feb '21

12 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=45286 Bug ID: 45286 Summary: when running microsoft office 2010 or 2007 it crashes at opening time Product: Wine Version: 3.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: oleaut32 Assignee: wine-bugs(a)winehq.org Reporter: i.bilux(a)gmail.com Distribution: --- Created attachment 61545 --> https://bugs.winehq.org/attachment.cgi?id=61545 debug file when running microsoft office 2010 or 2007 it crashes at opening time. i have tried everything, but it wont work ! the bug is in both wine staging 3.8 and 3.9. however wine staging 3.7 works fine. eventually i copied the "oleaut32.dll.so" file from wine staging 3.7 to wine staging 3.9 and it WORKED FINE ! ! ! so i'm pretty sure the fault is in the "oleaut32.dll.so" file. good luck and thank you. -- 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 12

[Bug 49284] New: Running "$ wine services" gives a list oferrors
by WineHQ Bugzilla 12 Feb '21

12 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=49284 Bug ID: 49284 Summary: Running "$ wine services" gives a list oferrors Product: Wine Version: 4.0.2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bart-wa(a)tushmail.com Distribution: --- Created attachment 67290 --> https://bugs.winehq.org/attachment.cgi?id=67290 This is file "Wine Services - output.txt" with the errors that I get. I recently started using Wine and I wonder if I bumped into a bug that's also the underlying problem of other bugs. Here's what happened: I had installed iTunes and I was hoping to get access to my iPhone via iTunes. (And I may not be the only one. ;-) ) I know that a few Apple services need to be running on a Windows computer for that. That's why I decided to check the services that were running under Wine. I started a terminal box, and I ran: $ wine services Before I knew it I had a decent list of errors on the screen. No problem, I've seen errors before in a lot of situations and from many programs. Since I wasn't running any third-party program, I wondered if this could be the underlying problem of other bugs. As a start I searched the bug list for "SIO_ADDRESS_LIST_CHANGE". That gave a list of seven other bugs and these users were all running different third-party programs. These other bugs may or may not be related. I find that difficult to tell, as I'm not yet familiar enough with Wine. Is this something that needs attention? Many thanks to all the nice people who make and maintain Wine! PS: - For "Severity" I choose "major", because I wasn't running any third-party software. Feel free to change this if you think I'm wrong. - For readability I added blank lines in attachment: "Wine Services - output.txt". - From time to time I try to look at things the way most users see them. That's also why I installed Wine via: Start -> Preferences -> Software -> Utilities This gives me wine version: wine-4.0 (Debian 4.0-2) , updated Apr. 22, 2020 - I'll be happy to install the latest development version next to the stable version that I have now, but I'll still have to figure out how to do that. - I'm running Linux/Debian 10 with LXDE graphical interface. -- 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 37612] New: Mount & Blade: Crashes on startup (No compatible Direct3D Device)
by wine-bugs＠winehq.org 12 Feb '21

12 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=37612 Bug ID: 37612 Summary: Mount & Blade: Crashes on startup (No compatible Direct3D Device) Product: Wine Version: 1.7.31 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: m22mail(a)comcast.net Mount & Blade: Warband crashes after the intro video with the error popup "Could not find any compatible 3D device". The game runs in Wine version 1.7.9 however it seems all the latest versions crash with this error. I installed all the DirectX .dlls from winecfg and installed the latest DirectX 9.0 Redistributable, but the crash remains. It seems as though this error happens when a video card does not meet the requirements, however I can confirm my card does meet the requirements, being that it opens in older versions of Wine. -- 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 42319] New: Uplay - Assassins Creed 1.x is crashing at lunch
by wine-bugs＠winehq.org 12 Feb '21

12 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=42319 Bug ID: 42319 Summary: Uplay - Assassins Creed 1.x is crashing at lunch Product: Wine-staging Version: 2.0-rc6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bog_dan_ro(a)yahoo.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Hi, I'm using wine-staging 2.0. Sadly I can't get the debug info because the debug window is unusable, is there any way to get the debug info? -- 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 10

[Bug 41011] New: foldit-linux wine crashes on start up
by wine-bugs＠winehq.org 12 Feb '21

12 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=41011 Bug ID: 41011 Summary: foldit-linux wine crashes on start up Product: Wine Version: 1.9.13 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: muns24072(a)mypacks.net Distribution: --- Created attachment 55178 --> https://bugs.winehq.org/attachment.cgi?id=55178 wine crash log for Foldit game foldit-linux wine crashes on start up -- 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 4

[Bug 49957] New: LibreOffice_7.0.1_Win_x64.msi gives error 0024:err:process:exec_process not supported on this system
by WineHQ Bugzilla 12 Feb '21

12 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=49957 Bug ID: 49957 Summary: LibreOffice_7.0.1_Win_x64.msi gives error 0024:err:process:exec_process not supported on this system Product: Wine Version: 5.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: cedric.dewijs(a)eclipso.eu Distribution: --- Created attachment 68349 --> https://bugs.winehq.org/attachment.cgi?id=68349 console messages Summary LibreOffice_7.0.1_Win_x64.msi gives error 0024:err:process:exec_process not supported on this system Download location https://www.libreoffice.org/download/download/ https://www.libreoffice.org/donate/dl/win-x86_64/7.0.1/en-US/LibreOffice_7.… $ sha256sum LibreOffice_7.0.1_Win_x64.msi a98ee61f915eb50853d08b0cfbefbb35bf610c0da4db8d4287415c64abce8c3c LibreOffice_7.0.1_Win_x64.msi Steps to reproduce 1) start the installer $ wine LibreOffice_7.0.1_Win_x64.msi This gives this error: "0024:err:process:exec_process L"Z:\\home\\cedric\\Downloads\\LibreOffice_7.0.1_Win_x64.msi" not supported on this system" -- 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 3

[Bug 42780] New: Bug Report relating to Blizzard clients ( possibly Battle net) used in logging to and playing Blizzard games
by wine-bugs＠winehq.org 12 Feb '21

12 Feb '21

https://bugs.winehq.org/show_bug.cgi?id=42780 Bug ID: 42780 Summary: Bug Report relating to Blizzard clients (possibly Battle net) used in logging to and playing Blizzard games Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: kleinthetraveler(a)gmail.com Distribution: --- Created attachment 57797 --> https://bugs.winehq.org/attachment.cgi?id=57797 Blizzard/Hearthstone Bug Tried to launch Hearthstone after downloading and installing from PlayOnLinux. Hearthstone login window pops up, but the client has no button to actually log in. -- 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 6