wine-bugs December 2022

wine-bugs@winehq.org

1 participants
3697 discussions

[Bug 54099] New: Stdout redirection broken when running Linux binaries
by WineHQ Bugzilla 28 Jan '23

28 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=54099 Bug ID: 54099 Summary: Stdout redirection broken when running Linux binaries Product: Wine Version: 7.22 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: dark.shadow4(a)web.de Distribution: --- Created attachment 73634 --> https://bugs.winehq.org/attachment.cgi?id=73634 Test program When running Linux binaries form inside Wine, using CreateProcessA, and redirecting stdout, it doesn't work. It works fine when executing Windows binaries. See attached test program. -- 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 52681] New: Google Chrome Stopped working after 7.2
by WineHQ Bugzilla 28 Jan '23

28 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=52681 Bug ID: 52681 Summary: Google Chrome Stopped working after 7.2 Product: Wine-staging Version: 7.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ndk+whq(a)esperanca.biz CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Hi! I have been using Google Chrome Portable for some time now. It was working with some options (--no-sandbox) right until wine-staging-7.3. It stopped starting after 7.3. The installation process from portableapps is smooth, it just does not want to start (no 'usual' black screen, just fails starting). I have tried to use old wine directory, new wine directory, installed corefonts as someone suggested in some of the bugs, etc. I also have tried to use wine-staging-7.4 with no luck. After I downgraded back to 7.2 - chrome started working again with --no-sandbox. The system: the latest Gentoo x64. Video card: AMD Radeon 480 (amdgpu Xorg driver). Command: WINEPREFIX=/path/to/wine wine /path/to/chrome --no-sandbox Expected Behavior (works until wine-staging-7.3): Chrome starts and is usable Actual Behavior (wine-staging-7.3; wine-staging-7.4): Chrome fails to start. Let me know if there are any debug info is needed (preferrably which options to enable for WINEDEBUG). -- 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

[Bug 53539] New: maybe a --with-wine-64 build should call widl with -win32 option
by WineHQ Bugzilla 28 Jan '23

28 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=53539 Bug ID: 53539 Summary: maybe a --with-wine-64 build should call widl with -win32 option Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: build-env Assignee: wine-bugs(a)winehq.org Reporter: j-r(a)online.de Distribution: --- Using just --with-wine-64 results in a Makefile calling widl from the win64 build directory without any target architecture specified resulting in early build failure: ... WIDL dlls/actxprxy/actxprxy_activscp_p.c WIDL dlls/actxprxy/actxprxy_activscp.h CC dlls/actxprxy/actxprxy_activscp_p.cross.o dlls/actxprxy/actxprxy_activscp_p.c:9084:2: error: #error Invalid build platform for this proxy. 9084 | #error Invalid build platform for this proxy. | ^~~~~ Hacking Makefile to add -win32 to the widl invocation works around this. I have no clue whether that is the right solution, 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.

1 8

[Bug 52567] New: 16-bit version of Project Pluto Guide 8.0 crashes on start with division by zero exception
by WineHQ Bugzilla 28 Jan '23

28 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=52567 Bug ID: 52567 Summary: 16-bit version of Project Pluto Guide 8.0 crashes on start with division by zero exception Product: Wine Version: 7.1 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alexhenrie24(a)gmail.com Distribution: --- Created attachment 71888 --> https://bugs.winehq.org/attachment.cgi?id=71888 Console output Steps to reproduce: 1. Run `wine setup16.exe` 2. Select "Windows 3.1 software (16 bit)" 3. Run `cd ~/.wine/drive_c/GUIDE8 && wine guide8a.exe` Console output 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.

1 6

[Bug 51427] New: CaptureAge crashes on startup
by WineHQ Bugzilla 26 Jan '23

26 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=51427 Bug ID: 51427 Summary: CaptureAge crashes on startup Product: Wine Version: 6.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: raphael.nestler(a)gmail.com Distribution: --- Created attachment 70280 --> https://bugs.winehq.org/attachment.cgi?id=70280 Console output of wine CaptureAge (https://appdb.winehq.org/objectManager.php?sClass=version&iId=39970) crashes on startup. After checking for updates it is just showing a white window before crashing. My System ArchLinux wine 6.12 from the ArchLinux repositories You can download CaptureAge from https://captureage.com/cade -- 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 6

[Bug 43188] New: Crash when accessing File Open dialog
by wine-bugs＠winehq.org 26 Jan '23

26 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=43188 Bug ID: 43188 Summary: Crash when accessing File Open dialog Product: Wine Version: 2.9 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: major Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: ph.schaefe(a)gmail.com Each time I use any of my windows programs with wine, and click the "Open File" menu item (or the "Open File ..." button) to get the 'file open dialog', the program crashes. This is consistent in all the windows programs I use. My version of Wine-devel seems up to date though, as I just did both "port upgrade wine-devel" and "port upgrade winetricks"on the console and it didn't upgrade anything. err:module:DelayLoadFailureHook failed to delay load comctl32.dll.HIMAGELIST_QueryInterface wine: Call from 0x7b42965e to unimplemented function comctl32.dll.HIMAGELIST_QueryInterface, aborting wine: Unimplemented function comctl32.dll.HIMAGELIST_QueryInterface called at address 0x7b42965e (thread 0009), starting debugger... Unhandled exception: unimplemented function comctl32.dll.HIMAGELIST_QueryInterface called in 32-bit code (0x7b42965e). -- 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 20

[Bug 38886] New: AArch64 platforms: ABI Problems wrt varargs (needs arm64 specific __builtin_ms_va_list)
by wine-bugs＠winehq.org 26 Jan '23

26 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=38886 Bug ID: 38886 Summary: AArch64 platforms: ABI Problems wrt varargs (needs arm64 specific __builtin_ms_va_list) Product: Wine Version: 1.7.46 Hardware: aarch64 URL: http://go.microsoft.com/fwlink/p/?LinkId=536682 OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: nerv(a)dawncrow.de CC: focht(a)gmx.net, nerv(a)dawncrow.de Distribution: --- Hi, running e.g. makecat.exe or midl.exe gives backtraces which suggest varargs problems. relevant part: (stripped) Backtrace: =>0 0x0000007f84d4aa04 raise_segv_exception(rec=0x7f83e8fa18, context=0x7f83e8f908) in ntdll (0x0000007f83e8fab0) 1 0x0000007f83d65864 pf_printf_w+0x8cb(pf_puts=0x7f83d61b18, puts_ctx=0x7f83e8fc70, fmt=<is not available>, locale=<is not available>, positional_params=0, invoke_invalid_param_handler=0x740020, pf_args=0x78003000200068, args_ctx=0x2d0020003a0000, valist=0x7f83e8fcb0) in msvcrt (0x0000007f83e8fab0) 2 0x0000007f83d65864 pf_printf_w+0x8cb(pf_puts=0x7f83d67ec0, puts_ctx=0x7f83e8fc70, fmt=<is not available>, locale=<is not available>, positional_params=0, invoke_invalid_param_handler=0, pf_args=0x7f83d617d8, args_ctx=0x0(nil), valist=0x7f83e8fcc8) in msvcrt (0x0000007f83e8fac0) 3 0x0000007f83d65864 pf_printf_w+0x8cb(pf_puts=0x7f836822c0, puts_ctx=0x0(nil), fmt=<is not available>, locale=<is not available>, positional_params=0x40020000, invoke_invalid_param_handler=0x7f, pf_args=0x140020000, args_ctx=0x140020000, valist=0x7f84280910) in msvcrt (0x0000007f83e8fc50) 4 0x0000007f83d67ec0 MSVCRT_vsnwprintf+0x47(str=<is not available>, len=<is not available>, format=<is not available>, valist={__stack=0x7f836819f0, __gr_top=0x140010170, __vr_top=0x7f8428071c, __gr_offs=0x83681a28, __vr_offs=0x7f}) in msvcrt (0x0000007f83e8fc80) 5 0x0000000140012328 in makecat (+0x12327) (0x0000007f83e8fcb0) 6 0x00000001400123b0 in makecat (+0x123af) (0x0000007f83e8fcb0) uuidgen.exe -i this generates a different path which involves MSVCRT_vsnprintf, pf_printf_a and pf_handle_string_a -- 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 24

[Bug 53946] New: Some applications produced with Delphi crash on Wine before WinMain
by WineHQ Bugzilla 25 Jan '23

25 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=53946 Bug ID: 53946 Summary: Some applications produced with Delphi crash on Wine before WinMain Product: Wine Version: 7.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mterrisse(a)free.fr Distribution: --- Created attachment 73522 --> https://bugs.winehq.org/attachment.cgi?id=73522 'Hello from Wine' compiled with Delphi and source code Wine 7.21 on Ubuntu 22.10 Hello, I attach a very small program built with Delphi 11.2 and source code (TestWine.dpr). It is a console application that says 'Hello from Wine' but it crashes on Wine, page fault. It works fine on Windows. I tried with winedbg and got this ========= 0084:fixme:wineusb:query_id Unhandled ID query type 0x5. 0084:fixme:wineusb:query_id Unhandled ID query type 0x5. 0084:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 0084:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 0084:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 0084:fixme:hid:handle_IRP_MN_QUERY_ID Unhandled type 00000005 WineDbg starting on pid 0120 0x000001700570a5 ntdll+0x570a5: ret Wine-dbg>0044:fixme:imm:ImeSetActiveContext (0000000000010026, 0): stub 0044:fixme:imm:ImmReleaseContext (0000000000010020, 0000000000010026): stub 012c:fixme:imm:ImeSetActiveContext (0000000000010052, 1): stub 012c:fixme:imm:ImmReleaseContext (0000000000030046, 0000000000010052): stub c Unhandled exception: page fault on execute access to 0x0000000000447000 in 64-bit code (0x00000000447000). Register dump: rip:0000000000447000 rsp:000000000057fe38 rbp:0000000000000000 eflags:00010a82 ( R- --O I S - - - ) rax:0000000170088050 rbx:0000000000000000 rcx:00000000003f0000 rdx:00000000004424c0 rsi:0000000000000000 rdi:0000000000000000 r8:00000000003f0000 r9:000000017007bca8 r10:0000000000000000 r11:0000000000000000 r12:0000000000000000 r13:0000000000000000 r14:0000000000000000 r15:0000000000000000 Stack dump: 0x0000000057fe38: 000000007b6291b9 0000000000000000 0x0000000057fe48: 000000000057fe90 0000000000000000 0x0000000057fe58: 0000000000000000 0000000000000000 0x0000000057fe68: 000000017005f8f3 0000000000000000 0x0000000057fe78: 0000000000000000 0000000000000000 0x0000000057fe88: 0000000000000000 00000000004424c0 0x0000000057fe98: 00000000003f0000 ffffffffffffffff 0x0000000057fea8: 000000017006ab30 0000000170027380 0x0000000057feb8: 0000000000000000 000000000057fea0 0x0000000057fec8: 0000000000000000 000000000057fe70 0x0000000057fed8: 0000000000000000 0000000000000000 0x0000000057fee8: 0000000000000000 0000000000000000 Backtrace: =>0 0x00000000447000 in testwine (+0x47000) (0000000000000000) 1 0x0000007b6291b9 BaseThreadInitThunk+0x9(unknown=<internal error>, entry=<internal error>, arg=<internal error>) [Z:\usr\src\packages\BUILD\dlls\kernel32\thread.c:61] in kernel32 (0000000000000000) 2 0x0000017005f8f3 __wine_pop_frame(entry=00000000004424C0, arg=00000000003F0000) [Z:\usr\src\packages\BUILD\include\wine\exception.h:277] in ntdll (0000000000000000) 3 0x0000017005f8f3 RtlUserThreadStart+0x83(entry=[<register RSP not accessible in this frame>, arg=[<register RSP not accessible in this frame>) [Z:\usr\src\packages\BUILD\dlls\ntdll\thread.c:285] in ntdll (0000000000000000) 0x00000000447000 testwine+0x47000: addb %al,(%rax) ========= I tried step by step but it seams that the code in WinMain function is never executed. Can you see what is wrong with this executable? Regards, Michel Terrisse -- 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 54157] New: dir command of cmd fails on Z: on Ubuntu under WSL
by WineHQ Bugzilla 25 Jan '23

25 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=54157 Bug ID: 54157 Summary: dir command of cmd fails on Z: on Ubuntu under WSL Product: Wine Version: 8.0-rc1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mterrisse(a)free.fr Distribution: --- Wine 8.0 rc1, Ubuntu 22.10 under WSL (Windows SubSystem for Linux, Windows 11 22H2) Hello, You will probably think it is a weird idea running Wine in Ubuntu under WSL. I tried it to avoid copying many files with my program to test it under Wine. I noticed this: wine64 cmd.exe dir This works fine on C: But if I do Z: dir I receive Invalid function. I tried this WINEDEBUG=warn+file wine64 cmd.exe Z: dir and there is something more explicit 0108:warn:file:get_mountmgr_fs_info failed to retrieve filesystem type from mountmgr, status 0xc000000e Invalid function. Do you know what is wrong? Regards, Michel Terrisse -- 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 14

[Bug 53224] New: Systray icon windows haven't a title
by WineHQ Bugzilla 25 Jan '23

25 Jan '23

https://bugs.winehq.org/show_bug.cgi?id=53224 Bug ID: 53224 Summary: Systray icon windows haven't a title Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: emonkak(a)gmail.com Distribution: --- According to System Tray Protocol Specification by freedesktop.org, the title should be set for the tray icon, but it isn't set. https://github.com/wine-mirror/wine/blob/e909986e6ea5ecd49b2b847f321ad89b2a… > _NET_WM_NAME, UTF8_STRING > > This hint should be set as it would be for a normal toplevel window, as defined in the Extended Window Manager Hints Specification (EWMH). The hint MUST be in UTF-8 encoding. It provides a human-readable, localized name for the tray icon. https://specifications.freedesktop.org/systemtray-spec/systemtray-spec-0.2.… -- 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 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs December 2022