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

[Bug 47915] New: League of Legends 9.20: Crash after champ select
by WineHQ Bugzilla June 7, 2021

June 7, 2021

https://bugs.winehq.org/show_bug.cgi?id=47915 Bug ID: 47915 Summary: League of Legends 9.20: Crash after champ select Product: Wine Version: 4.17 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mail+wine(a)m-reimer.de Distribution: --- Created attachment 65411 --> https://bugs.winehq.org/attachment.cgi?id=65411 Crash dump Since updating to LoL 9.20 there is a new "crash after champ select" issue. Probably this is the anticheat, again. Would be great if some experienced developer could have a look at this. I've attached my crash dump but the bug is really easy to reproduce. Just try to open the "practice tool". Will crash immediately when the switch from client to actual game should happen. Maybe Andrew Wesie could have a look at this one? He did an remarkably great job with fixing such things in the past! -- 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 49

[Bug 48043] New: user32:dce has a pair of random failures
by WineHQ Bugzilla June 4, 2021

June 4, 2021

https://bugs.winehq.org/show_bug.cgi?id=48043 Bug ID: 48043 Summary: user32:dce has a pair of random failures Product: Wine Version: unspecified Hardware: x86 OS: Windows Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Created attachment 65584 --> https://bugs.winehq.org/attachment.cgi?id=65584 user32:dce: Loop over the test_destroyed_window() for 2 random failures. user32:dce has a pair of random failures in test_destroyed_window(): dce.c:648: Test failed: wrong window dce.c:658: Test failed: DC for destroyed window not reused One either gets the first one alone or both together. See https://test.winehq.org/data/tests/user32:dce.html These happen at random on a wide range of Windows versions: wxppro, w2003std, w2008s64, fg-win7u64-*, w1064v1507, w1064v1607. On Windows 10 the same type of error sometimes happens in test_dc_attributes() on line 127 which is another "wrong window\n" check. The attached patch loops over test_destroyed_window() which is sufficient to make these failures systematic. This can hopefully help debug the issue and make sure these are 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.

1 3

[Bug 15781] New: Can't run AllInOne-Office 5
by wine-bugs＠winehq.org June 4, 2021

June 4, 2021

http://bugs.winehq.org/show_bug.cgi?id=15781 Summary: Can't run AllInOne-Office 5 Product: Wine Version: 1.1.7 Platform: Other URL: http://www.allinone-office.de/ OS/Version: other Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: dank(a)kegel.com A user asked for this package here: http://www.linux-forum.de/warenwirtschaft-allione-5-0-a-20117.html so I tried installing it. First, you have to set your language to German, e.g. LANG=DE_de.UTF-8 or it commplains about a language mismatch. Then, you have to set your Windows version to NT 4 with winecfg, else it complains that it needs Windows NT 4 or higher. Then it installs. The font in the installer is almost too tiny to read, even with corefonts installed. It first silently installs the Access 2002 runtime libraries and Jet 40, and those subinstallers aren't particularly happy; they both end with err:msi:ITERATE_Actions Execution halted, action L"InstallFinalize" returned 1627 but the main installer continues blindly. It asks if you want to keep the existing version of some wine dll; I said yes. It installs a menu item showing that the way to run the app is wine "C:\\Program Files\\Common Files\\Microsoft Shared\\Access Runtime\\Office10\\MSAccess.exe" /Runtime "C:\\Program Files\\AllInOne-Office\\AllInOne-Office.mde" but that fails with file not found... maybe because of the access runtime installation problem? -- 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 13

[Bug 47180] New: Nocturne unhandled exception bug on startup
by wine-bugs＠winehq.org June 4, 2021

June 4, 2021

https://bugs.winehq.org/show_bug.cgi?id=47180 Bug ID: 47180 Summary: Nocturne unhandled exception bug on startup Product: Wine Version: 4.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jagsoul87(a)gmail.com Distribution: --- Created attachment 64434 --> https://bugs.winehq.org/attachment.cgi?id=64434 Unhandled exception register dump/log file When trying to run Nocturne the game crashes displaying an error message, when I click on "show details" it shows the following message: Unhandled exception: page fault on read access to 0x00000000 in 32-bit code. The following register dump and full log file it's attached to this bug report. -- 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 8

[Bug 41253] New: GZDoom Builder : Unable to make a new project
by wine-bugs＠winehq.org June 4, 2021

June 4, 2021

https://bugs.winehq.org/show_bug.cgi?id=41253 Bug ID: 41253 Summary: GZDoom Builder : Unable to make a new project Product: Wine Version: 1.9.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: janusczpawlacz(a)protonmail.ch Distribution: --- Created attachment 55547 --> https://bugs.winehq.org/attachment.cgi?id=55547 Terminal error outpot of Builder.exe So every time I try to open a new project or opening a existing map for editing a error appears and it just plain crashes. Error Message: Fatal Windows Forms error occured: CompilationException While [unreadable] Fatal Windows Forms Error http://devbuilds.drdteam.org/doombuilder2-gzdb/GZDoom%20Builder%20R2364%20I… sha1sum: aa65a19b1275deb09680f4227f81218d27308422 Distribution: Linux Mint 18 Mate X86_64 (64bit) -- 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 46320] New: Kindle don't get installed: abnormal program temrination
by wine-bugs＠winehq.org June 4, 2021

June 4, 2021

https://bugs.winehq.org/show_bug.cgi?id=46320 Bug ID: 46320 Summary: Kindle don't get installed: abnormal program temrination Product: Wine Version: 4.0-rc2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: raffamaiden(a)gmail.com Distribution: --- Created attachment 63054 --> https://bugs.winehq.org/attachment.cgi?id=63054 command line log file + screenshot Kindle for PC version 1.24.51068 don't even get installed. After the installer showing up the dialog in which it says it is decompressing the files, after the dialog in which it says it is copying (I presume?) the files, an error message shows up "abnormal program termination" I attach log and screenshot -- 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 48094] New: Simplify debugging test timeouts
by WineHQ Bugzilla June 4, 2021

June 4, 2021

https://bugs.winehq.org/show_bug.cgi?id=48094 Bug ID: 48094 Summary: Simplify debugging test timeouts Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: testcases Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- When a Wine test times out one has to manually add traces to figure out where it gets stuck, or what the slow parts are. This is all the more difficult when the timeout is random and happens on a TestBot VM. I propose to leverage the ok() calls to simplify getting timing information on the tests. * Recognize the $WINETEST_TIME environment variable and, if it is set, add the elapsed time since the test started to the trace() and ok() messages. * Ideally this elapsed time would have sub-second precision for those cases where it's more an issue of a long loop being slow. How many decimals to print is a matter of taste: one may be enough, three would feel quite standard if maybe a bit overkill. * Also when $WINETEST_TIME is set, an ok() call would be printed even if successful when more than 1 second has elapsed since adding a message to the report (trace/ok/skip). This should allow identifying which part of the test causes trouble without altering its timing with thousands of traces. * And when combined with $WINETEST_REPORT_SUCCESS of course every ok() call would print the elapsed time. Once the Wine side is implemented a few other components should be updated: * The TestBot should allow setting $WINETEST_TIME when submitting a job. * The TestBot should recognize the failure/todo/skip lines even with the extra timing information. * The TestBot could be modified to automatically rerun and set $WINETEST_TIME if a test times out. * The above may be particularly interesting for the full WineTest runs. * We may also want to have test.winehq.org recognize the new failure/todo/skip line formats. -- 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 34746] New: Dino Crisis Demo doesn't play video sequences even though Indeo codecs are installed
by wine-bugs＠winehq.org June 4, 2021

June 4, 2021

http://bugs.winehq.org/show_bug.cgi?id=34746 Bug #: 34746 Summary: Dino Crisis Demo doesn't play video sequences even though Indeo codecs are installed Product: Wine Version: 1.7.4 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: winebugs140(a)gmail.com Classification: Unclassified Created attachment 46322 --> http://bugs.winehq.org/attachment.cgi?id=46322 Dino Crisis Demo Log without Indeo Tested with: Ubuntu 13.04, GeForce 9600M GS (NVIDIA driver 313) Mac OS X 10.7.5, ATI HD 2600 Pro, Mac Driver/X11 -- 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 19

[Bug 31310] New: TIE: Fighter: Collectors Edition -- Application Crashes on Launch
by wine-bugs＠winehq.org June 4, 2021

June 4, 2021

http://bugs.winehq.org/show_bug.cgi?id=31310 Bug #: 31310 Summary: TIE: Fighter: Collectors Edition -- Application Crashes on Launch Product: Wine Version: 1.5.9 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: muleyryan(a)fastmail.fm Classification: Unclassified Wine running on 3.4.6-1-ARCH, with S3 Inc. SuperSavage IX/C SDR (rev 05) xf86-video-savage and MESA savage drivers installed. Using gdi as d3d renderer. Application (TIE95.exe) crashes on launch Backtrace here: http://pastebin.com/mTX4bPet Regression test pending. -- 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 10

[Bug 49801] New: Freight Yard Manager: Crashes on start
by WineHQ Bugzilla June 4, 2021

June 4, 2021

https://bugs.winehq.org/show_bug.cgi?id=49801 Bug ID: 49801 Summary: Freight Yard Manager: Crashes on start Product: Wine Version: 5.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: blue(a)blu3wolf.com Distribution: --- Created attachment 68114 --> https://bugs.winehq.org/attachment.cgi?id=68114 exception text On running, Freight Yard Manager V5.9.17 (and all previous versions tested) throws an unhandled System.InvalidProgramException: Invalid IL code. This does not happen on any tested Windows 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 18