wine-bugs June 2021

wine-bugs@winehq.org

1 participants
5071 discussions

[Bug 46718] New: IDispatch.Invoke cause 80020005 error on out IUnknown Param
by wine-bugs＠winehq.org 12 Nov '22

12 Nov '22

https://bugs.winehq.org/show_bug.cgi?id=46718 Bug ID: 46718 Summary: IDispatch.Invoke cause 80020005 error on out IUnknown Param Product: Wine-staging Version: 3.0 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alexeev(a)krista.ru CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 63688 --> https://bugs.winehq.org/attachment.cgi?id=63688 AutoObjectCmd.exe test with required lib IDispatch.Invoke cause 80020005 error on out IUnknown param, when call argument is IDispatch. Sounds like right result, but Windows try to cast out parameter to argument type. Attached application with library should fail in Wine on such call - simple run AutoObjectCmd.exe. -- 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 3

[Bug 29974] New: StarBurn crashes on disabling skins
by wine-bugs＠winehq.org 11 Nov '22

11 Nov '22

http://bugs.winehq.org/show_bug.cgi?id=29974 Bug #: 29974 Summary: StarBurn crashes on disabling skins Product: Wine Version: 1.4-rc4 Platform: x86-64 URL: http://www.starburnsoftware.com/products/starburn/down load/download-starburn-free OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: uxtheme AssignedTo: wine-bugs(a)winehq.org ReportedBy: RandomAccountName(a)mail.com Classification: Unclassified Created attachment 39020 --> http://bugs.winehq.org/attachment.cgi?id=39020 Terminal output StarBurn crashes a moment after disabling skins within the program. This option is at view -> skin -> disable. Workaround: native uxtheme.dll -- 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 47412] New: Kaseya Live Connect: crashes on first run after install
by wine-bugs＠winehq.org 09 Nov '22

09 Nov '22

https://bugs.winehq.org/show_bug.cgi?id=47412 Bug ID: 47412 Summary: Kaseya Live Connect: crashes on first run after install Product: Wine Version: 4.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: registry Assignee: wine-bugs(a)winehq.org Reporter: alero5752(a)hotmail.com Distribution: --- Created attachment 64760 --> https://bugs.winehq.org/attachment.cgi?id=64760 Progam Error details Hello, Linux noob here. My company recently upgraded our Kaseya VSA version to 9.5.0.2 and ever since this was completed it broke my Kaseya Live Connect app compatibility within Wine. I've attached the log to review and also a link to the EXE file for the application below. This is the very latest version of Kaseya. When attempting to launch the program, it stops and displays an error, (The program QtWebEngineProcess.exe has encountered a serious problem and needs to close. We are sorry for the inconvenience). https://drive.google.com/file/d/1StEVxsaQFKTVX8pb6htmo8r_4R14btJz/view?usp=… -- 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 3

[Bug 34377] New: Paint Shop Pro X5 Installer fails
by wine-bugs＠winehq.org 09 Nov '22

09 Nov '22

http://bugs.winehq.org/show_bug.cgi?id=34377 Bug #: 34377 Summary: Paint Shop Pro X5 Installer fails Product: Wine Version: 1.6 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: maikwagner(a)yahoo.com Classification: Unclassified Created attachment 45757 --> http://bugs.winehq.org/attachment.cgi?id=45757 Backtrace Hello everyone, I have been testing "Paint Shop Pro X5" from Corel but I am having problems to get it to install correctly. Please find my backtrace attached and please let me know should you require further information. -- 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 21

[Bug 12732] New: Nota Bene crashes on install
by wine-bugs＠winehq.org 08 Nov '22

08 Nov '22

http://bugs.winehq.org/show_bug.cgi?id=12732 Summary: Nota Bene crashes on install Product: Wine Version: CVS/GIT Platform: PC URL: https://www.notabene.com/download/demos/nbdemo80.exe OS/Version: Linux Status: NEW Keywords: download, Installer, win16 Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com Testing for bug 11023 I found that nota bene will no longer install. I'll start the regression test... -- 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 45

[Bug 50433] New: 'MsiBreak' custom action debugging aid should use custom action's name from 'CustomAction' table (currently uses 'Target' field)
by WineHQ Bugzilla 08 Nov '22

08 Nov '22

https://bugs.winehq.org/show_bug.cgi?id=50433 Bug ID: 50433 Summary: 'MsiBreak' custom action debugging aid should use custom action's name from 'CustomAction' table (currently uses 'Target' field) Product: Wine Version: 6.0-rc4 Hardware: x86-64 OS: Linux Status: NEW Severity: trivial Priority: P2 Component: msi Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, I always have to remember that Wine uses 'Target' field/name from the 'CustomAction' table instead of the custom action's name when debugging custom actions. Fooled me quite a number of times in these 13 years. I'm aware that very few people might be concerned/affected with this inconsistency but still. https://docs.microsoft.com/en-us/windows/win32/msi/debugging-custom-actions I requested the installer debugging aid in 2007 in bug 8243 ("Feature: Add MsiBreak to aid debugging custom actions"): https://source.winehq.org/git/wine.git/commitdiff/60e95ee6e8ea4a4f43a6c170c… ("msi: Add handling for MsiBreak.") My follow-up comment https://bugs.winehq.org/show_bug.cgi?id=8243#c7 was ignored. Maybe because I didn't bother to create a follow-up bug and/or didn't complain loud enough ;-) --- quote --- Please fix the evaluation to use "action" msi_custom_action_info member instead of "target" to make it feature compatible with Windows MSI server. --- quote --- Some example (from bug 21987): --- snip --- ... 01b0:trace:msi:ACTION_CustomAction Handling custom action L"CreateAdobePDFPrinter" (c41 L"AdobeIsf" L"SetupAdobePDFPrinter") ... 01b0:trace:msi:HANDLE_CustomType1 Calling function L"SetupAdobePDFPrinter" from L"C:\\users\\focht\\Temp\\msi48b7.tmp" ... 02f8:Ret PE DLL (proc=0160618A,module=01600000 L"msi48b7.tmp",reason=PROCESS_ATTACH,res=00000000) retval=1 ... 02f8:Ret KERNEL32.LoadLibraryW() retval=01600000 ret=100210f6 02f8:Call KERNEL32.GetProcAddress(01600000,0016df28 "SetupAdobePDFPrinter") ret=1002110a 02f8:Ret KERNEL32.GetProcAddress() retval=01602bea ret=1002110a ... --- snip --- To have this work for Wine 'MsiBreak=SetupAdobePDFPrinter' is needed but 'MsiBreak=CreateAdobePDFPrinter' would be correct. $ wine --version wine-6.0-rc4 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 6

[Bug 50869] New: Regressions caused by new start.exe behaviour in Wine 6.5 (stdout redirect, killing inferior, wine start /unix)
by WineHQ Bugzilla 08 Nov '22

08 Nov '22

https://bugs.winehq.org/show_bug.cgi?id=50869 Bug ID: 50869 Summary: Regressions caused by new start.exe behaviour in Wine 6.5 (stdout redirect, killing inferior, wine start /unix) Product: Wine Version: 6.5 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: programs Assignee: wine-bugs(a)winehq.org Reporter: mail(a)robbertvanderhelm.nl Distribution: --- I noticed a few regressions and new weird behaviours after updating to Wine 6.5 with regards to launching applications now that everything gets launched through start.exe: 1. When launching Winelib applications all STDOUT output gets lost. I tested this with a simple C++ file compiled with wineg++ that tries to print some text using both `printf()` and `std::cout`. Printing to STDERR using `std::cerr` still works fine. 2. When spawning a Wine child process from another application, you can no longer kill that child process by raising SIGINT or SIGKILL for the pid of the child. In Wine 6.5 this now kills the start.exe process, but it leaves the inferior process running in the background. To reproduce this, run `wine notepad&` in `fish` (bash seems to kill the child process by itself), use `ps -aux | grep notepad` or `jobs` to find the pid of the process just named `notepad`, and then run `kill -SIGKINT <pid>` (or with SIGKILL). Even though the process launched using `wine notepad&` has exited, Notepad is still running in the background. 3. (duplicate of bug 50867, but I still wanted to mention it here for completeness' sake) Launching binaries with Wine from the GUI by clicking on them (using the bundled wine.desktop) no longer works. This uses `wine start /unix`, which was already reported to no longer work as of Wine 6.5 in the other issue because `ShellExecuteEx` cannot find the file. 4. And lastly, as discovered by @stefand, `wine https://google.com` now launches the regular system browser. This is probably not really a bug as much as a consequence of the start.exe change, but I just wanted to mention it. Please let me know if I should split this up into separate tickets. -- 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 16

[Bug 50352] New: Maximum sockets per process is set very low
by WineHQ Bugzilla 08 Nov '22

08 Nov '22

https://bugs.winehq.org/show_bug.cgi?id=50352 Bug ID: 50352 Summary: Maximum sockets per process is set very low Product: Wine Version: 5.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winsock Assignee: wine-bugs(a)winehq.org Reporter: skreech(a)skree.ch Distribution: --- Created attachment 68942 --> https://bugs.winehq.org/attachment.cgi?id=68942 TWGS warning at startup Within wine-5.22/dlls/ws2_32/socket.c, the maximum number of sockets per process is set and used like so: > #define WS_MAX_SOCKETS_PER_PROCESS 128 /* reasonable guess */ and: > lpWSAData->iMaxSockets = WS_MAX_SOCKETS_PER_PROCESS; This became relevant when I ran the TradeWars 2002 game server (TWGS) under a maximum license allowing 100 simultaneous players. On startup, it logs a message warning that the OS's number of sockets per process is limited to 128, therefore no more than 63 players will be able to connect. This makes sense, since two sockets are required per player connection, and one SysOp connection is reserved. Changing WS_MAX_SOCKETS_PER_PROCESS to 1024 and recompiling WINE results in TWGS not experiencing this limit and not giving the warning. Also, I tested TWGS under ReactOS and did not experience limit nor warning. Peeking into their socket.c, I notice that their limit is set to 32767, or 0, depending: https://github.com/reactos/reactos/search?q=iMaxSockets It seems likely that WS_MAX_SOCKETS_PER_PROCESS should be set to 32767 here if any value is being set, given that the underlying OS should be the one imposing its own limits or lack of limit. -- 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 44202] New: undname.c fails to parse symbols with rvalue-reference semantics '&&'
by wine-bugs＠winehq.org 08 Nov '22

08 Nov '22

https://bugs.winehq.org/show_bug.cgi?id=44202 Bug ID: 44202 Summary: undname.c fails to parse symbols with rvalue-reference semantics '&&' Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: shulgaaa(a)gmail.com Distribution: --- For example, the symbol ??4QDnsDomainNameRecord@@QAEAAV0@$$QAV0@@Z should be de-mangled as: public: class QDnsDomainNameRecord & __thiscall QDnsDomainNameRecord::operator=(class QDnsDomainNameRecord &&) undname returns NULL -- 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 17

[Bug 50370] New: Gothic 1 doesn't start correctly when screen resolution of the game matches display resolution
by WineHQ Bugzilla 08 Nov '22

08 Nov '22

https://bugs.winehq.org/show_bug.cgi?id=50370 Bug ID: 50370 Summary: Gothic 1 doesn't start correctly when screen resolution of the game matches display resolution Product: Wine Version: 5.13 Hardware: x86-64 URL: https://www.fileplanet.com/archive/p-5260/Gothic-Demo- English OS: Linux Status: NEW Keywords: download, regression Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com CC: rbernon(a)codeweavers.com Regression SHA1: f90d607c67768f19e36d9d74b498594252faa3fd Distribution: --- I'm starting Gothic 1 v1.08k using in-game resolution 1440x900 which matches my native display resolution. The game does start up because I can hear the sound of the intro movie, but no visible window is created (the screen is black). This used to work up until commit f90d607c67768f19e36d9d74b498594252faa3fd ddraw: Use the WINED3D_SWAPCHAIN_NO_WINDOW_CHANGES flag. Reverting that commit on top of 6.0-rc3 fixes the problem for me. To reproduce the problem in the demo: 1. Before starting the game modify GOTHIC.INI located in the Program Files/Piranha Bytes/Gothic 1 Demo/system directory. Look for the section [Video] and change in-game screen resolution there so that it matches your display resolution: zVidResFullscreenX= zVidResFullscreenY= You also need to set 32-bit color depth (the problem doesn't occur with 16-bit): zVidResFullscreenBPP=32 2. run gothic.exe setupg1demo-en.exe md5sum: 2932bcb79118abadca0d394a7a86c096 wine-6.0-rc3 OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce GT 730/PCIe/SSE2 OpenGL core profile version string: 4.6.0 NVIDIA 455.46.04 -- 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 19

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 June 2021