December 2023 - Wine-bugs - list.winehq.org

[Bug 52547] New: GIMP 2.2.x: Mouse disappears and is ignored by the application
by WineHQ Bugzilla 14 Jan '24

14 Jan '24

https://bugs.winehq.org/show_bug.cgi?id=52547 Bug ID: 52547 Summary: GIMP 2.2.x: Mouse disappears and is ignored by the application Product: Wine Version: 7.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: joseskvolpe(a)gmail.com Distribution: --- Mouse pointer disappears and won't work in most places of the interface, however, the application seems to detect when the pointer (wich is invisible) is hovering over buttons, but doesn't recognize mouse clicks. On Windows 10, mouse events has the expected behavior and the mouse pointer changes to another offered by the application. Procedure: 1 - Run GIMP-2.0/bin/gimp-2.2.exe 2 - Move mouse over windows and click on it's contents Download: GIMP 2.2.17: http://www.oldversion.com/windows/the-gimp-2-2-17 SHA1: bb8a3e297d6f2885c80c394901380b81d8ae0a67 Although the applications requests for GTK+ 2.4.14, GTK+ 2.10.13 is required to install this application GTK+ 2.10.13: https://sourceforge.net/projects/gtk-win/files/GTK%2B%20Runtime%20Environme… SHA1: bc5902c48590413fdd57ece9b69ee478849329c9 -- 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 7

[Bug 21215] New: New Star Soccer 2010 crashes when starting a new career
by wine-bugs＠winehq.org 14 Jan '24

14 Jan '24

http://bugs.winehq.org/show_bug.cgi?id=21215 Summary: New Star Soccer 2010 crashes when starting a new career Product: Wine Version: 1.1.35 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: lminiero(a)gmail.com New Star Soccer 2010 crashes when you try to start a new career. You can customize your profile correctly, but when you confirm your choices, and the database is created for you, halfway though the process Wine crashes. Everything else (main menu, game engine itself) works correctly. It has been verified (not by me) that loading an already saved game (e.g. saved in Windows) works fine, so the problem is in generating the savegame database. The game has a debug mode, which shows that the last operation printed on console (be it completed or still ongoing) is a 'DoLeagueElimination' (you can choose, in the customization process, which leagues you want to be accessible during the game). I'll attach a back trace. -- 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 39

[Bug 41915] New: Crimzon Clover WORLD IGNITION - No music playback, sound effects missing
by wine-bugs＠winehq.org 14 Jan '24

14 Jan '24

https://bugs.winehq.org/show_bug.cgi?id=41915 Bug ID: 41915 Summary: Crimzon Clover WORLD IGNITION - No music playback, sound effects missing Product: Wine Version: 1.9.23 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: irrenhaus3(a)gmail.com Distribution: --- Created attachment 56296 --> https://bugs.winehq.org/attachment.cgi?id=56296 wine output, up until the game shows its loading screen The Steam version of Yotsubane's shooting game "Crimzon Clover WORLD IGNITION" doesn't play any background music, misses most of its sound effects and the few effects it does play are not mixed properly (most of the time they are too loud). I believe this bug to be OpenAL-related due to this specific line in the log: err:winediag:IXAudio2Impl_CreateSourceVoice OpenAL ran out of sources, consider increasing its source limit. This bug still prevails in 1.9.23, but it has been present for roughly 2 or 3 earlier releases in the winehq-repository. Thank you for your time. -- 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 43677] New: Act of Aggression - Stuck on loading screen
by wine-bugs＠winehq.org 14 Jan '24

14 Jan '24

https://bugs.winehq.org/show_bug.cgi?id=43677 Bug ID: 43677 Summary: Act of Aggression - Stuck on loading screen Product: Wine Version: 2.15 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: supagu(a)gmail.com Distribution: --- Running from steam, it first tries to install some of the usual libs that steam does and then run the game: https://pastebin.com/fkwYwgK5 -- 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 55289] New: undefined reference to `wWinMain'
by WineHQ Bugzilla 13 Jan '24

13 Jan '24

https://bugs.winehq.org/show_bug.cgi?id=55289 Bug ID: 55289 Summary: undefined reference to `wWinMain' Product: Wine Version: 8.11 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winecrt0 Assignee: wine-bugs(a)winehq.org Reporter: esteve.varela(a)gmail.com Distribution: --- I can't get wineg++ -mconsole -municode to correctly attempt to call wmain instead of wWinMain: $ echo '#include <stddef.h>\nint wmain(int argc,wchar_t *argv[]){return 0;}' > test.c $ wineg++ -mconsole -municode test.c /usr/lib/gcc/x86_64-pc-linux-gnu/12/../../../../x86_64-pc-linux-gnu/bin/ld: /usr/lib/wine-staging-8.11/bin/../wine/x86_64-unix/libwinecrt0.a(exe_wmain.o): in function `wmain': (.text+0x9b): undefined reference to `wWinMain' collect2: error: ld returned 1 exit status winegcc: /usr/bin/x86_64-pc-linux-gnu-g++ failed This issue is reproducible on both Debian 12 and Gentoo, using winehq-8.11. -- 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 49936] New: modal dialog box behaves modeless
by WineHQ Bugzilla 13 Jan '24

13 Jan '24

https://bugs.winehq.org/show_bug.cgi?id=49936 Bug ID: 49936 Summary: modal dialog box behaves modeless Product: Wine Version: 5.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ch.panel(a)free.fr Distribution: --- Creating a modal dialog box in an MDI environment : when this one has for parent an MDI Child window, this behaves like a modeless window (bug because MDI child was expecting an answer) when this one has for parent the Application Frame window (parent of parent... of MDI Child window), this behaves correctly (modal). It's like wine doesn't manage MDI model correctly... -- 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 7

[Bug 52966] New: user32:combo - test_listbox_size() fails in Wine in the Japanese locale
by WineHQ Bugzilla 13 Jan '24

13 Jan '24

https://bugs.winehq.org/show_bug.cgi?id=52966 Bug ID: 52966 Summary: user32:combo - test_listbox_size() fails in Wine in the Japanese locale Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: user32 Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- user32:combo - test_listbox_size() fails in Wine in the Japanese locale: combo.c:798: Test marked todo: Test 1, expected list height to be 0, got 14 combo.c:798: Test failed: Test 2, expected list height to be 0, got 15 combo.c:798: Test failed: Test 11, expected list height to be 0, got 15 combo.c:798: Test succeeded inside todo block: Test 15, expected list height to be 54, got 54 https://test.winehq.org/data/patterns.html#user32:combo This is readily reproducible with: (just make sure to have the required locale in locale -a) LANG=ja_JP.UTF-8 ./wine dlls/user32/tests/user32_test.exe combo -- 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 2

[Bug 55710] New: wine-staging fails to run anything in 64-bit prefix
by WineHQ Bugzilla 12 Jan '24

12 Jan '24

https://bugs.winehq.org/show_bug.cgi?id=55710 Bug ID: 55710 Summary: wine-staging fails to run anything in 64-bit prefix Product: Wine-staging Version: 8.17 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dmitry(a)baikal.ru CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Even an attemp to create new 64-bit prefix fails: $ WINEPREFIX=~/.wine64 WINEARCH=win64 ~/wine-staging64/wine winver wine: created the configuration directory '/home/dmitry/.wine64' 002c:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0) 002c:fixme:winediag:LdrInitializeThunk wine-staging 8.17 is a testing version containing experimental patches. 002c:fixme:winediag:LdrInitializeThunk Please mention your exact version when filing bug reports on winehq.org. 002c:fixme:sync:NtAcceptConnectPort ((nil),832,0x90000002,31,0x7ffffe0ff338,0x7d7d011256a0),stub! *** stack smashing detected ***: <unknown> terminated 002c:err:seh:call_stack_handlers invalid frame 00007FFFFE0FF320 (00007FFFFE102000-00007FFFFE200000) 002c:err:seh:NtRaiseException Exception frame is not in stack limits => unable to dispatch exception. With 32-bit prefix everything seems to work. It looks like this problem started with wine-staging 8.16. -- 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 39

[Bug 52491] New: SpaceDesk: Error when trying to connect to the server now but it worked in 6.10 and below
by WineHQ Bugzilla 12 Jan '24

12 Jan '24

https://bugs.winehq.org/show_bug.cgi?id=52491 Bug ID: 52491 Summary: SpaceDesk: Error when trying to connect to the server now but it worked in 6.10 and below Product: Wine Version: 7.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jota0222(a)hotmail.com Distribution: --- Created attachment 71785 --> https://bugs.winehq.org/attachment.cgi?id=71785 Log Of SpaceDesk Runinng After the release of stable 7.0.0, I noticed that SpaceDesk stoped working and then I tried some older versions versions, none of the listed to register the apps in the WineHQ page worked (6.21 and above), however it worked in all the ones below 6.10. I didn't try with the ones in between, so I don't really know when the bug was introduced exactly. The app doesn't throw exceptions or show error in logs, the log attached is basically the same in both 6.10 and 7.0.0 versions. I also tried with winedbg but if I dissable $BreakOnFirstChance it never stops on any exception and the log finish up being the same as the one attached (at least doesn't looks like it's showing things related to the issue). And if I run it with $BreakOnFirstChance set as 1, it's impossible to reach the moment of in which the error occurs due to al the exceptions in which it stops before to even show the window. This image shows the error: https://paste.pics/FTUXV -- 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 11

[Bug 38780] New: AArch64 platforms: register X18 must remain reserved for Wine to run 64-bit ARM Windows applications (Distro aarch64 toolchains need '-ffixed-x18' default, loader/libc/userland)
by wine-bugs＠winehq.org 12 Jan '24

12 Jan '24

https://bugs.winehq.org/show_bug.cgi?id=38780 Bug ID: 38780 Summary: AArch64 platforms: register X18 must remain reserved for Wine to run 64-bit ARM Windows applications (Distro aarch64 toolchains need '-ffixed-x18' default, loader/libc/userland) Product: Wine Version: 1.7.45 Hardware: aarch64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, split off from bug 38719 ("64-bit ARM Windows applications from Windows SDK for Windows 10 crash when accessing TEB/PEB members (AArch64 platform specific register X18 must be reserved for TEB)") Resolution is 'upstream' here, the Wine part is bug 38719 http://infocenter.arm.com/help/topic/com.arm.doc.ihi0055b/IHI0055B_aapcs64.… Chapter 5 "THE BASE PROCEDURE CALL STANDARD" --- quote --- The role of register r18 is platform specific. If a platform ABI has need of a dedicated general purpose register to carry interprocedural state (for example, the thread context) then it should use this register for that purpose. If the platform ABI has no such requirements, then it should use r18 as an additional temporary register. The platform ABI specification must document the usage for this register. Note Software developers creating platform independent code are advised to avoid using r18 if at all possible. Most compilers provide a mechanism to prevent specific registers from being used for general allocation; portable hand-coded assembler should avoid it entirely. It should not be assumed that treating the register as callee saved will be sufficient to satisfy the requirements of the platform. Virtualization code must, of course, treat the register as they would any other resource provided to the virtual machine. --- quote --- 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.

2 37