wine-bugs September 2022

wine-bugs@winehq.org

1 participants
3425 discussions

[Bug 36989] New: ThunderSpeed installer get white blank window
by wine-bugs＠winehq.org 28 May '23

28 May '23

http://bugs.winehq.org/show_bug.cgi?id=36989 Bug ID: 36989 Summary: ThunderSpeed installer get white blank window Product: Wine Version: 1.7.23 Hardware: x86 URL: http://down.sandai.net/thunderspeed/ThunderSpeed1.0.12 .122.exe OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: penghao(a)linuxdeepin.com Created attachment 49129 --> http://bugs.winehq.org/attachment.cgi?id=49129 installer window under wine inlinux Environment: Deepin 32bit Linux phcole 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:12 UTC 2014 i686 i686 i686 GNU/Linux wine-1.7.23 download from: http://down.sandai.net/thunderspeed/ThunderSpeed1.0.12.122.exe start it to install the program, I get white blank window instead. -- 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 18

[Bug 24878] New: "Group by" options don't work in Explorer++
by wine-bugs＠winehq.org 28 May '23

28 May '23

http://bugs.winehq.org/show_bug.cgi?id=24878 Summary: "Group by" options don't work in Explorer++ Product: Wine Version: 1.3.5 Platform: x86-64 URL: http://www.explorerplusplus.com/download OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: comctl32 AssignedTo: wine-bugs(a)winehq.org ReportedBy: RandomAccountName(a)mail.com Created an attachment (id=31495) --> (http://bugs.winehq.org/attachment.cgi?id=31495) Terminal output The file grouping options accessible in the view -> group by menu don't seem to do anything. Native comctl32 (v6) makes them functional. -- 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 41223] New: IDA MDI doesn't have scrollbars when it should
by wine-bugs＠winehq.org 28 May '23

28 May '23

https://bugs.winehq.org/show_bug.cgi?id=41223 Bug ID: 41223 Summary: IDA MDI doesn't have scrollbars when it should Product: Wine Version: 1.9.17 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: comctl32 Assignee: wine-bugs(a)winehq.org Reporter: b7.10110111(a)gmail.com Distribution: --- Created attachment 55488 --> https://bugs.winehq.org/attachment.cgi?id=55488 How it looks in Wine To reproduce: 1. Launch IDA, have it maximized 2. Open a file, so that IDA begins analysis 3. Unmaximize main window 4. See lack of scrollbars in the MDI, despite child windows being too large to fit. 5. Compare the same with Windows and see that there it does have the scrollbars. The only thing I get in the console is this: fixme:win:LockWindowUpdate (0x500c4), partial stub! fixme:win:LockWindowUpdate ((nil)), partial stub! fixme:win:LockWindowUpdate (0x500c4), partial stub! fixme:win:LockWindowUpdate ((nil)), partial stub! -- 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 52012] New: MeshroomCL crashes on unimplemented function vcomp140.dll._vcomp_for_dynamic_init_i8
by WineHQ Bugzilla 28 May '23

28 May '23

https://bugs.winehq.org/show_bug.cgi?id=52012 Bug ID: 52012 Summary: MeshroomCL crashes on unimplemented function vcomp140.dll._vcomp_for_dynamic_init_i8 Product: Wine Version: 6.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: vcomp Assignee: wine-bugs(a)winehq.org Reporter: revisionarian(a)gmail.com Distribution: --- The photogrammetry software application MeshroomCL crashes during execution of its TexturingCL node. The output error message is: "Unhandled exception: unimplemented function vcomp140.dll._vcomp_for_dynamic_init_i8 called in 64-bit code" This error was encountered using Wine 6.21 on Unbuntu 20.04. MeshroomCL version was 0.7.3. MeshroomCL can be downloaded from URL https://github.com/openphotogrammetry/meshroomcl/releases. -- 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 27559] New: ImgBurn crash at startup when Wine's 'Windows Version' is set to 'Vista' (or newer)
by wine-bugs＠winehq.org 27 May '23

27 May '23

http://bugs.winehq.org/show_bug.cgi?id=27559 Summary: ImgBurn crash at startup when Wine's 'Windows Version' is set to 'Vista' (or newer) Product: Wine Version: 1.3.22 Platform: x86 URL: http://www.imgburn.com/ OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: lightning_uk(a)imgburn.com I've had a bunch of crash logs sent to me over the past year where ImgBurn crashes unrecoverably on startup when users are running it under Wine but was never able to reproduce the error until today. It turns out that if Wine's 'Windows Version' is set to 'XP' (default and what I'd always been using) everything works fine. The second it's changed to 'Vista' (or newer), the app crashes at startup. I've managed to get a crash call stack via madExcept / Eurekalog and have now traced the problem back to the 'Explorer' style component it uses in the 'Disc Layout Editor' window ('TVirtualExplorerTree' by MustangPeak). It looks like it's related to namespace stuff and therefore the shell? I've made/attached a Delphi demo app with a single form and single instance of 'TVirtualExplorerTree' to hopefully make testing and debugging this issue a little easier. Without fail, it'll crash when Wine's 'Windows Version' is set to 'Vista' but it's fine as 'XP'. I'm using Wine in Ubuntu 11.04 for testing. The programs (ImgBurn and demo app) work fine on a real Windows XP, Vista or 7 installation. -- 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 33

[Bug 50955] New: .netCore app can't bind to port shortly after another .netCore program binding to the same port was terminated
by WineHQ Bugzilla 26 May '23

26 May '23

https://bugs.winehq.org/show_bug.cgi?id=50955 Bug ID: 50955 Summary: .netCore app can't bind to port shortly after another .netCore program binding to the same port was terminated Product: Wine Version: 6.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: besentv(a)gmail.com Distribution: --- Created attachment 69784 --> https://bugs.winehq.org/attachment.cgi?id=69784 BrokenClient I provided code for 3 different programs as attachment which represent extremely scaled down code of a bug I tried to find in a proprietary program: BrokenServer and BrokenClient are both C# programs created for .netCore 3.1 (x86). BrokenServer creates a socket, tries to bind it to port 41811 and ends up accepting all incoming connections on this port inside an infinite loop. Broken Client tries to connect to the socked opened by BrokenServer and ends up in an infinite loop(seems important!?). TestCode is to test what is actually broken in Wine: It runs a BrokenServer and 3 BrokenClients using CreateProcessA() and waits for getchar(). After that it stops all 4 processes using TerminateProcess() and immediately restarts the BrokenServer using CreateProcessA(). The server tries to bind to port 41811 but unlike on Windows it (almost) always fails to do so, showing a MessageBox with the information that the port is already in use. As mentioned before, the infinite loop in BrokenClient seems to make a difference because I never encountered this issue without it. I wasn't able to recreate this problem with native code. Everything was tested in a clean prefix with .netCore x86 desktop ("windowsdesktop-runtime-3.1.10-win-x86") installed. -- 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 10

[Bug 36230] New: qcap: Silverlight requires Audio Capture Filter
by wine-bugs＠winehq.org 26 May '23

26 May '23

http://bugs.winehq.org/show_bug.cgi?id=36230 Bug ID: 36230 Summary: qcap: Silverlight requires Audio Capture Filter Product: Wine Version: 1.7.18 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: michael(a)fds-team.de Silverlight requires the "Audio Capture Filter" for recording from the microphone. Steps to reproduce (Download Silverlight + start configuration dialog): wget http://silverlight.dlservice.microsoft.com/download/B/A/9/BA94BEC9-5DBC-4B5… wine Silverlight.exe wine "C:\Program Files\Microsoft Silverlight\5.1.30214.0\Silverlight.Configuration.exe" Change to the Webcam and Microphone Tab. The list of devices is empty and you should see the following debug messages: ------- err:ole:CoGetClassObject no class object {e30629d2-27e5-11ce-875d-00608cb78066} could be created for context 0x17 fixme:strmbase:STRMBASE_DllGetClassObject {e30629d2-27e5-11ce-875d-00608cb78066}: class not implemented yet. ------- The CLSID belongs to CLSID_AudioRecord and is not implemented in dlls/qcap/qcap_main.c (/* FIXME: Implement QCAP_createAudioCaptureFilter */) -- 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 18

[Bug 53717] New: Unreadable CDROM disk freezes wine
by WineHQ Bugzilla 26 May '23

26 May '23

https://bugs.winehq.org/show_bug.cgi?id=53717 Bug ID: 53717 Summary: Unreadable CDROM disk freezes wine Product: Wine Version: 7.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: winebugs(a)copysoft.org Distribution: --- I'm trying to recover data from an almost unreadable CDROM disk. I have been running ddrescue non-stop for a few days now and data is slowly being recovered. This means the CDROM drive is permanently busy at all times with a disk that is unreadable and unmountable under normal circumstances (this is important). When I try to launch a wine application via Wine I find that Wine attempts to access the CDROM drive, I can hear the CDROM drive making noises as if starting/stopping but nothing ever happens, can hear the drive clicking as in starting and stopping, the wine application I'm trying to run never start, I can see some wine .exe processes in D state, I guess waiting for the CDROM drive to become available. I can see this in the console: 0058:err:sync:RtlpWaitForCriticalSection section 000000006CDCB040 "dlls/mountmgr.sys/device.c: device_section" wait timed out in thread 0058, blocked by 0064, retrying (60 sec) It seems that when a drive is unreadable or inaccessible wine freezes and continually re-tries access to the drive. This also means that Wine interferes with ddrescue when trying to access the CDROM drive, because the disk is unreadable and both applications try to access no Wine application ever starts, and if it does (winecfg) it freezes, so I end in a situation Wine doesn't work and it bothers ddrescue. Is there a way to start Wine applications making them ignore the CDROM Drive? In the Wine control panel I can get rid of the Z drive for example but not the CDROM drive... I also tried to go into the Wine prefix under "dosdevices" and removed: d:: -> /dev/sr0 Then tried to link d:: to /dev/null but wine recreates the link to the drive as e:: -> /dev/sr0 and tries to access the CDROM again. Is there a way to tell WINE not to use a device? as in ignore /dev/sdr? -- 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 50369] New: Multiple tools for viewing GDI handles/resources list and GDI leak detection require support for PEB->GdiSharedHandleTable (GDIView, GDILeaks)
by WineHQ Bugzilla 25 May '23

25 May '23

https://bugs.winehq.org/show_bug.cgi?id=50369 Bug ID: 50369 Summary: Multiple tools for viewing GDI handles/resources list and GDI leak detection require support for PEB->GdiSharedHandleTable (GDIView, GDILeaks) Product: Wine Version: 6.0-rc3 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, as it says. I know this information can be retrieved tracing processes with Wine 'gdi' debug channel. https://source.winehq.org/git/wine.git/blob/56e7cd12ce0ce3bb331a8595b25aedb… Currently investigating bug 23221 where the application massively leaks GDI handles. App bug, most likely unrelated to the actual problem of the ticket. I wanted to see the leakage in a realtime-view with absolute values, leak rate per second, changes when doing certain UI actions. It's possible to extract that from Wine trace logs as well using timestamps and filtering for specific messages but it takes way more effort to associate the leak rate with certain UI actions (controls). Multiple tools provide that information in a convenient way. Unfortunately they rely on the shared handle table being exposed. --- * https://www.nirsoft.net/utils/gdi_handles.html ("GDIView - View GDI handles/resources list and detect GDI leaks") Stable download link via Internet Archive: https://web.archive.org/web/20201127182337/http://www.nirsoft.net/utils/gdi… * https://docs.microsoft.com/en-us/archive/msdn-magazine/2003/january/detect-… ("Detect and Plug GDI Leaks in Your Code with Two Powerful Tools for Windows XP") Stable download link via Internet Archive: https://web.archive.org/web/20170911002438/http://download.microsoft.com/do… The MSDN article provides the struct layout for entry: --- quote --- In his book Windows Graphics Programming: Win32 GDI and DirectDraw (Prentice Hall, 2002), Feng Huan provides another way to access this table, but he also describes the structure of each of the 0x4000 entries of this table, as you can see here: ... typedef struct { DWORD pKernelInfo; WORD ProcessID; WORD _nCount; WORD nUpper; WORD nType; DWORD pUserInfo; } GDITableEntry; --- quote --- 'GDILeaks' self-extractor contains multiple example applications as binaries and with sources. https://www.geoffchappell.com/studies/windows/win32/ntdll/structs/peb/index… --- quote --- Offset (x86) Offset (x64) Definition Versions 0x94 0xF8 PVOID GdiSharedHandleTable; 3.51 and higher --- quote --- The app crashes because the 'PEB->GdiSharedHandleTable' pointer is NULL: --- snip --- $ WINEDEBUG=+seh,+relay wine ./GDIView.exe >>log.txt 2>&1 ... 0104:Call KERNEL32.GetModuleHandleW(140011eb0 L"ntdll.dll") ret=140004c52 ... 0104:Ret KERNEL32.GetModuleHandleW() retval=7bc00000 ret=140004c52 0104:Call KERNEL32.GetProcAddress(7bc00000,140011ec8 "RtlGetCurrentPeb") ret=140004c67 0104:Ret KERNEL32.GetProcAddress() retval=7bc068e4 ret=140004c67 0104:Call ntdll.RtlGetCurrentPeb() ret=140004c6e 0104:Ret ntdll.RtlGetCurrentPeb() retval=7fffffdaf000 ret=140004c6e 0104:trace:seh:dispatch_exception code=c0000005 flags=0 addr=0000000140004CA6 ip=0000000140004CA6 tid=0104 0104:trace:seh:dispatch_exception info[0]=0000000000000000 0104:trace:seh:dispatch_exception info[1]=0000000000000008 0104:trace:seh:dispatch_exception rax=0000000000000000 rbx=0000000000f314c0 rcx=000000000021ee48 rdx=0000000000000000 0104:trace:seh:dispatch_exception rsi=0000000000000000 rdi=0000000000000000 rbp=0000000000000000 rsp=000000000021edf8 0104:trace:seh:dispatch_exception r8=000000000021ee30 r9=0000000000000000 r10=0000000000000000 r11=0000000000000246 0104:trace:seh:dispatch_exception r12=0000000000000415 r13=0000000000000001 r14=0000000000000000 r15=000000000021f168 0104:trace:seh:call_vectored_handlers calling handler at 000000007B011BA0 code=c0000005 flags=0 0104:trace:seh:call_vectored_handlers handler at 000000007B011BA0 returned 0 0104:warn:seh:virtual_unwind exception data not found in L"GDIView.exe" --- snip --- Wine source: --- snip --- $ grep -Hrni GdiSharedHandleTable include/winternl.h:339: PVOID GdiSharedHandleTable; /* 094/0f8 */ include/winternl.h:584: ULONG64 GdiSharedHandleTable; /* 00f8 */ --- snip --- https://source.winehq.org/git/wine.git/blob/56e7cd12ce0ce3bb331a8595b25aedb… (x86) https://source.winehq.org/git/wine.git/blob/56e7cd12ce0ce3bb331a8595b25aedb… (x86_64) $ sha1sum gdiview*.zip 4bacc3fed9a41678c72eba41937ff73b7e98ee90 gdiview-x64.zip 1115a41a1784127380ac2df0d3960f4bf09955db gdiview.zip $ du -sh gdiview*.zip 68K gdiview-x64.zip 52K gdiview.zip $ wine --version wine-6.0-rc3 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.

1 4

[Bug 53392] New: does not compile on Openindiana (solaris11)
by WineHQ Bugzilla 23 May '23

23 May '23

https://bugs.winehq.org/show_bug.cgi?id=53392 Bug ID: 53392 Summary: does not compile on Openindiana (solaris11) Product: Wine Version: 7.13 Hardware: x86-64 OS: Solaris Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: malicorne(a)chez.com It seems that wine does not respect the CFLAGS or at least to some extend. $ uname -a SunOS addie 5.11 illumos-c1bbf9203b i86pc i386 i86pc illumos $ ./configure CFLAGS="-fPIC" CXXFLAGS="-fPIC" --prefix=/opt/wine $ make [...] gcc -o tools/winegcc/winegcc tools/winegcc/utils.o tools/winegcc/winegcc.o -lsocket -lnsl tools/winegcc/winegcc -o dlls/acledit/acledit.dll.so --wine-objdir . -fno-PIC -fasynchronous-unwind-tables -shared \ dlls/acledit/acledit.spec -Wb,--prefer-native -mno-cygwin dlls/acledit/main.o \ dlls/winecrt0/libwinecrt0.a dlls/ucrtbase/libucrtbase.a dlls/kernel32/libkernel32.a \ dlls/ntdll/libntdll.a Text relocation remains referenced against symbol offset in file .rodata (section) 0x11010 acledit.dll-62d91a2e.spec.o .rodata (section) 0x11017 acledit.dll-62d91a2e.spec.o .rodata (section) 0x11030 acledit.dll-62d91a2e.spec.o .rodata (section) 0x11037 acledit.dll-62d91a2e.spec.o .rodata (section) 0x11050 acledit.dll-62d91a2e.spec.o .rodata (section) 0x11057 acledit.dll-62d91a2e.spec.o .rodata (section) 0x11070 acledit.dll-62d91a2e.spec.o .rodata (section) 0x11077 acledit.dll-62d91a2e.spec.o .rodata (section) 0x11090 acledit.dll-62d91a2e.spec.o .rodata (section) 0x11097 acledit.dll-62d91a2e.spec.o .rodata (section) 0x110b0 acledit.dll-62d91a2e.spec.o .rodata (section) 0x110b7 acledit.dll-62d91a2e.spec.o .data (section) 0x110d5 acledit.dll-62d91a2e.spec.o .data (section) 0x110f1 acledit.dll-62d91a2e.spec.o .data (section) 0x11102 acledit.dll-62d91a2e.spec.o .data (section) 0x1110a acledit.dll-62d91a2e.spec.o .data (section) 0x11112 acledit.dll-62d91a2e.spec.o .data (section) 0x1111a acledit.dll-62d91a2e.spec.o .data (section) 0x11122 acledit.dll-62d91a2e.spec.o ld: fatal: relocations remain against allocatable but non-writable sections collect2: error: ld returned 1 exit status winegcc: /usr/bin/gcc failed make: *** [Makefile:1380: dlls/acledit/acledit.dll.so] Error 2 Error on line 4 If I replace the -fno-PIC by -fPIC as requested on CFLAGS, it does go on until next 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.

1 15

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 September 2022