June 2025 - Wine-Bugs - list.winehq.org

[Bug 58378] New: VirtualBox 4.3.40: Crash on start

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=58378 Bug ID: 58378 Summary: VirtualBox 4.3.40: Crash on start Product: Wine Version: 10.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: kyle.kcsoftwares(a)gmail.com Distribution: --- Install VirtualBox 4.3.40 https://download.virtualbox.org/virtualbox/4.3.40/VirtualBox-4.3.40-110317-… Installer faces https://bugs.winehq.org/show_bug.cgi?id=56815 but installs When starting Virtual Box log shows : wine VirtualBox.exe 002c:fixme:winediag:loader_init wine-staging 10.10 is a testing version containing experimental patches. 002c:fixme:winediag:loader_init Please mention your exact version when filing bug reports on winehq.org. 0098:fixme:ntoskrnl:MmGetSystemRoutineAddress L"HalSendSoftwareInterrupt" not found 0098:fixme:ntoskrnl:MmGetSystemRoutineAddress L"KeIpiGenericCall" not found 0098:fixme:ntoskrnl:MmGetSystemRoutineAddress L"KeQueryInterruptTimePrecise" not found 0098:fixme:ntoskrnl:MmGetSystemRoutineAddress L"KeQuerySystemTimePrecise" not found 0098:fixme:ntoskrnl:MmGetSystemRoutineAddress L"PsIsProtectedProcessLight" not found 0098:fixme:ntoskrnl:MmGetSystemRoutineAddress L"ZwAlpcCreatePort" not found wine: Unhandled page fault on read access to FFFFFFFFFFFFFFFF at address 00000001004112D3 (thread 0098), starting debugger... 00c0:err:ole:start_rpcss Failed to start RpcSs service 00b8:err:ole:start_rpcss Failed to start RpcSs service 00c0:err:ole:start_rpcss Failed to start RpcSs service 00a8:fixme:dbghelp:elf_search_auxv can't find symbol in module 00a8:fixme:dbghelp:elf_search_auxv can't find symbol in module 003c:err:service:process_send_command service protocol error - failed to read pipe r = 0 count = 0! 003c:fixme:service:scmdatabase_autostart_services Auto-start service L"VBoxDrv" failed to start: 1053 0024:fixme:winediag:loader_init wine-staging 10.10 is a testing version containing experimental patches. 0024:fixme:winediag:loader_init Please mention your exact version when filing bug reports on winehq.org. wine: Unhandled page fault on read access to 000000000000000F at address 00000001400169AB (thread 018c), starting debugger... 0194:fixme:dbghelp:elf_search_auxv can't find symbol in module 0194:fixme:dbghelp:elf_search_auxv can't find symbol in module then Debugger opens and shows: Unhandled exception: page fault on read access to 0x000000000000000f in 64-bit code (0x000001400169ab). Register dump: rip:00000001400169ab rsp:000000000011ea50 rbp:000000000011eb50 eflags:00010246 ( R- -- I Z- -P- ) rax:00000000fffffff2 rbx:00000000000001f5 rcx:000000000000004b rdx:000000014007c974 rsi:00000000000001f6 rdi:00000000000001f6 r8:00000001400aa7a0 r9:00006fffffa20080 r10:00006fffffa63000 r11:00000000001c1000 r12:000000014007d000 r13:00000001400aa6ec r14:0000000000000000 r15:0000000000000960 Stack dump: 0x0000000011ea50: 00000001400aa7a0 000000000011eb50 0x0000000011ea60: 0000000000000001 00000001400aa7c8 0x0000000011ea70: 0000000000000000 0000000000000000 0x0000000011ea80: 0000000000000000 0000000000000000 0x0000000011ea90: 0000000000000000 0000000000000000 0x0000000011eaa0: 0000000000000000 0000000000000000 0x0000000011eab0: 0000000000000000 0000000000000000 0x0000000011eac0: 0000000000000000 0000000000000000 0x0000000011ead0: 0000000000000000 0000000000000000 0x0000000011eae0: 0000000000000000 0000000000000000 0x0000000011eaf0: 0000000000000000 0000000000000000 0x0000000011eb00: 0000000000000000 0000000000000000 Backtrace: =>0 0x000001400169ab in virtualbox (+0x169ab) (0x0000000011eb50) 1 0x00000140007044 in virtualbox (+0x7044) (0000000000000000) 2 0x006fffffa34949 BaseThreadInitThunk+0x9(unknown=<internal error>, entry=<internal error>, arg=<internal error>) [/usr/src/packages/BUILD/dlls/kernel32/thread.c:61] in kernel32 (0000000000000000) 3 0x006fffffc0fdb3 in ntdll (+0xfdb3) (0000000000000000) 0x000001400169ab virtualbox+0x169ab: movb 0xf, %al Modules: Module Address Debug info Name (10 modules) PE 140000000- 1400ee000 --none-- virtualbox PE-Wine 6fffff3d0000- 6fffffa0b000 Deferred kernelbase PE-Wine 6fffffa20000- 6fffffbe1000 Dwarf-4 kernel32 PE-Wine 6fffffc00000- 6ffffffe3000 Dwarf-4 ntdll ELF 720518afd000- 720518c00000 Export ntdll.so ELF 720518c00000- 720518e20000 Deferred libc.so.6 ELF 720518e60000- 720518ea0000 Deferred liblzma.so.5 ELF 720518ea0000- 720518ebb000 Deferred libunwind.so.8 ELF 720518ed4000- 720518f12000 Deferred ld-linux-x86-64.so.2 ELF 720518f12000- 720518f17000 Deferred <wine-loader> -- 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.

June 16, 2025

[Bug 23193] wine notepad: Slow to open large files

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=23193 KRosUser <kyle.kcsoftwares(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kyle.kcsoftwares(a)gmail.com --- Comment #22 from KRosUser <kyle.kcsoftwares(a)gmail.com> --- Worth being retested. Talking about ReactOS in your previous comment, they still face some performance issue : https://jira.reactos.org/browse/CORE-19898 -- 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.

June 16, 2025

[Bug 57828] Approach Smart Icons do not show

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=57828 --- Comment #14 from Todd Chester <ToddAndMargo(a)zoho.com> --- Extra info: I just remembered another virtual machine where the Smart Icon bar does show: $ cat /etc/redhat-release Fedora release 42 (Adams) $ rpm -qa wine\* wine-stable-10.0.0-1.1.x86_64 winehq-stable-10.0.0-1.1.x86_64 -- 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.

June 16, 2025

[Bug 58377] winegcc -m32 fails to link when using the new WoW64 mode

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=58377 --- Comment #1 from Alexandre Julliard <julliard(a)winehq.org> --- 32-bit ELF dlls cannot be built in new wow64 mode, since the whole idea is to not use 32-bit Unix libraries. If you want to support new wow64 with a 32-bit binary, the only way is to build it as PE. If you need to make Unix calls you have to create a separate Unix library and use the WINE_UNIX_CALL interface. This is still a work in progress as far as Winelib is concerned though. -- 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.

June 16, 2025

[Bug 58377] New: winegcc -m32 fails to link when using the new WoW64 mode

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=58377 Bug ID: 58377 Summary: winegcc -m32 fails to link when using the new WoW64 mode Product: Wine Version: 10.9 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winelib Assignee: wine-bugs(a)winehq.org Reporter: mail(a)robbertvanderhelm.nl Distribution: --- Created attachment 78787 --> http://bugs.winehq.org/attachment.cgi?id=78787 winegcc command output Prompted by Arch switching to the new WoW64 mode in their packages. 32-bit winelib binaries seem to fail to link with the new WoW64 mode. I attached the output of compiling the following file with winegcc from a Wine build configured with `--enable-archs=i386,x86_64`: /* main.c */ int main() { return 0; } /* compiled with: LANG=C wineg++ -v -m32 -lole32 -o main main.c */ Swapping `-m32` out for `-m64` the winelib binary builds as expected. Most notably, the underlying GCC invocations include both `-m64` and `-m32` in that order (though it may have always done that), and the core Windows libraries cannot be found (which kind of makes sense since Wine no longer ships actual 32-bit libraries). On a related note: is it possible to detect whether Wine has been configured with the new WoW64 mode? I may need to detect this at runtime to be able to distribute a build of yabridge that works with both the old and new WoW64 modes. -- 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.

June 16, 2025

[Bug 58376] New: -

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=58376 Bug ID: 58376 Summary: - Product: Wine Version: 10.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: z60235022(a)gmail.com Distribution: --- Created attachment 78786 --> http://bugs.winehq.org/attachment.cgi?id=78786 - При запуске Lesta Происходит ошибка Chrome OS -- 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.

June 16, 2025

[Bug 57828] Approach Smart Icons do not show

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=57828 Janne <janne.kekkonen(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |janne.kekkonen(a)gmail.com --- Comment #13 from Janne <janne.kekkonen(a)gmail.com> --- (In reply to Todd Chester from comment #7) > (In reply to Janne from comment #6) > > > Do you have Lotus Notes installed? > > Ignore the nNOTES.dll error. It is a bug in Smart Suite and appears in > native Windows installation as well. It does not affect anything. > > > Were you able to get your View -> show -> Smart Icons" bar? I got approach to run. I had to copy everything from lotus/component to lotus/approach directory. I also got SmartIcons bar to show from. File-> User Setup -> Smart Icon Setup. I had to create new SmartIcons bar. When bar was created it was floating near Approach window as separate window. But it could be dragged & anchored next to menus. When approach was stopped and re-started, SmartIcon bar was gone from GUI. -- 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.

June 16, 2025

[Bug 58375] Fatal error when trying to run Hitman 3

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=58375 --- Comment #1 from nro <mfuyami16(a)gmail.com> --- Created attachment 78785 --> http://bugs.winehq.org/attachment.cgi?id=78785 log from my command shell when trying to open the executable from there -- 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.

June 16, 2025

[Bug 58375] New: Fatal error when trying to run Hitman 3

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=58375 Bug ID: 58375 Summary: Fatal error when trying to run Hitman 3 Product: Wine Version: 10.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mfuyami16(a)gmail.com Distribution: --- Created attachment 78784 --> http://bugs.winehq.org/attachment.cgi?id=78784 backtrace from trying to open the main executable, hitman3.exe When trying to run the game Hitman 3, I get a fatal error report. The launcher opens normally, but when I press play, it crashes entirely. I tried opening it from the terminal, and the same thing happens. I am not an experienced user of either Linux or Wine, but I have installed and successfully run several other games on the same device. I have restarted the computer multiple times and even tried redownloading the game, with no effect. The backtrace from Wine is attached. -- 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.

June 16, 2025

[Bug 58371] Battlefield 2 Caps Lock menu annoying pop ups

by WineHQ Bugzilla

http://bugs.winehq.org/show_bug.cgi?id=58371 totibuluduj(a)punkproof.com changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|INVALID |--- Version|unspecified |10.0 Status|RESOLVED |UNCONFIRMED --- Comment #4 from totibuluduj(a)punkproof.com --- Opened a new bug since this was erroneously marked as invalid. -- 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.

June 16, 2025