https://bugs.winehq.org/show_bug.cgi?id=53309
Bug ID: 53309
Summary: Wizard101 launcher window takes over a minute to
appear
Product: Wine
Version: 7.12
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: regression
Severity: normal
Priority: P2
Component: secur32
Assignee: wine-bugs(a)winehq.org
Reporter: dimesio(a)earthlink.net
CC: hans(a)meelstraat.net
Regression SHA1: 0a10bfc8b17234db6aff130ce0448a62c3fb6a1e
Distribution: SUSE
Normally it pops up immediately.
0a10bfc8b17234db6aff130ce0448a62c3fb6a1e is the first bad commit
commit 0a10bfc8b17234db6aff130ce0448a62c3fb6a1e
Author: Hans Leidekker <hans(a)codeweavers.com>
Date: Wed Jun 29 13:54:57 2022 +0200
secur32: Return a SECBUFFER_MISSING buffer from the handshake if the input
message is incomplete.
dlls/secur32/schannel.c | 25 +++++++++++++++++++++++--
dlls/secur32/tests/schannel.c | 21 ++++++++++++++++++++-
2 files changed, 43 insertions(+), 3 deletions(-)
Reverting the patch fixes it.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=53104
Bug ID: 53104
Summary: Wireshark can't start capturing packets
Product: Wine
Version: 7.10
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wpcap
Assignee: wine-bugs(a)winehq.org
Reporter: rpisl(a)seznam.cz
Distribution: ---
Created attachment 72539
--> https://bugs.winehq.org/attachment.cgi?id=72539
Patch for wpcap
While testing bug 53066 I just wanted to find out what would be needed to make
Wireshark working in Wine. There are two obvious problems:
1. pcap_create() doesn't translate interface identifier to the real name
2. pcap_dispatch() is not implemented
I fixed these problems, however, packet window still remains empty after
capture is started while the temporary capture file is filled with captured
packets. If this temporary file is later opened, Wireshark shows all packets
captured.
Attached is the patch if someone wants to push this further. "setcap
cap_net_raw,cap_net_admin=eip wine64-preloader" is needed to give Wine
permissions to capture packets.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=51129
Bug ID: 51129
Summary: Function name conflict (ldap_connect) with OpenLDAP
2.5
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wldap32
Assignee: wine-bugs(a)winehq.org
Reporter: sergio.durigan(a)canonical.com
Distribution: ---
Hello,
Wine installs the "/usr/include/wine/wine/windows/winldap.h" file, which
exports the ldap_connect function:
ULONG CDECL ldap_connect(LDAP*,struct l_timeval*);
With the recent OpenLDAP 2.5 release, we now have an "ldap_connection" function
being exported by it as well (with a different prototype):
https://git.openldap.org/openldap/openldap/-/blame/OPENLDAP_REL_ENG_2_5_4/i…
This will need to be fixed in order to prevent linking problems with OpenLDAP.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=53355
Bug ID: 53355
Summary: Missing functions SystemTimeToTzSpecificLocalTimeEx
and TzSpecificLocalTimeToSystemTimeEx
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: osmanx(a)problemloesungsmaschine.de
Distribution: ---
Created attachment 72743
--> https://bugs.winehq.org/attachment.cgi?id=72743
tz.exe
Please implement SystemTimeToTzSpecificLocalTimeEx and
TzSpecificLocalTimeToSystemTimeEx. The documentation can be found at
<https://docs.microsoft.com/en-us/windows/win32/api/timezoneapi/nf-timezonea…>
and
<https://docs.microsoft.com/en-us/windows/win32/api/timezoneapi/nf-timezonea…>.
Note that because these functions currently outright abort, the work-around I
implemented requires explicitly detecting Wine and not even trying to call
them, which is far from optimal.
Even just implementing stubs that always fail gracefully instead of just
aborting the whole process would be much appreciated.
This came up when improving local timezone handling in OpenMPT. See
<https://bugs.openmpt.org/view.php?id=1618> and
<https://source.openmpt.org/browse/openmpt?op=comp&compare[]=/trunk/OpenMPT/…>.
Simple test case (for SystemTimeToTzSpecificLocalTimeEx):
tz.cpp:
```
#include <iostream>
#include <stdexcept>
#include <windows.h>
int main() {
try {
SYSTEMTIME sys{};
GetSystemTime(&sys);
DYNAMIC_TIME_ZONE_INFORMATION dtzi{};
if (GetDynamicTimeZoneInformation(&dtzi) == TIME_ZONE_ID_INVALID) {
throw std::runtime_error("GetDynamicTimeZoneInformation()
failed.");
}
SYSTEMTIME sys_local{};
if (SystemTimeToTzSpecificLocalTimeEx(&dtzi, &sys, &sys_local) ==
FALSE) {
throw std::runtime_error("SystemTimeToTzSpecificLocalTimeEx()
failed.");
}
std::cout << "OK" << std::endl;
return 0;
} catch (const std::exception & e) {
std::cout << std::flush;
std::cerr << e.what() << std::endl;
std::cerr << std::flush;
}
std::cout << "FAIL" << std::endl;
return 1;
}
```
built with VS2022 by running `cl /std:c++20 /permissive- /EHsc /O2 /W4 tz.cpp`
results in
```
wine: Call from 0x7bc7c990 to unimplemented function
KERNEL32.dll.SystemTimeToTzSpecificLocalTimeEx, aborting
```
not even reaching the FAIL output. tz.exe 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.
https://bugs.winehq.org/show_bug.cgi?id=53347
Bug ID: 53347
Summary: Xerox Globalview gives missing DSD.386, won't start
Product: Wine
Version: 6.0.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: aa271828(a)earthlink.net
Distribution: ---
Created attachment 72733
--> https://bugs.winehq.org/attachment.cgi?id=72733
terminal output file
I installed Globalview in wine 6.0.2, when I run it GVWIN.EXE I get a popup
saying "Disk Virtual device driver DSD.386 is not loaded"
--
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.
https://bugs.winehq.org/show_bug.cgi?id=2948
temp82(a)luukku.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |temp82(a)luukku.com
--- Comment #25 from temp82(a)luukku.com ---
(In reply to joaopa from comment #24)
> Bug still occurs with wine-7.0-rc5.
and still valid as of wine 7.12.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=50890
Bug ID: 50890
Summary: Honey Select Unlimited - Character Models Don't Render
On-Screen
Product: Wine
Version: 6.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: gregory(a)opera.id.au
Distribution: ---
Created attachment 69702
--> https://bugs.winehq.org/attachment.cgi?id=69702
Screenshot of issue (character model *should* show in center of screen)
When launching "Honey Select Unlimited", character models do not render
on-screen (nothing appears)... Everything else (sound, menus, backgrounds,
etc...) seems to work; it is only the character models that seem to be
affected.
As it is only the character models that seem to be affected, this suggests that
the issue lies with something in the way the character models are rendered in
the game / simulation.
In order to progress in the game / simulation, one must interact with the
characters almost immediately, so this bug is game / simulation-breaking (i.e.
the game / simulation cannot be used via WINE whilst this bug is present).
This bug also affects "Honey Studio", which is a separate program, but one that
is included as a part of the "Honey Select Unlimited" installation.
Honey Select Unlimited version 1.0.2 was used when experiencing / testing /
replicating this bug.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=53338
Bug ID: 53338
Summary: Vba71-kb2783832-x64.msp installation
Product: Wine
Version: 7.12
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: msi
Assignee: wine-bugs(a)winehq.org
Reporter: windes(a)rambler.ru
Distribution: ---
Good day!
Why this simple installation of Vba71-kb2783832-x64.msp file always fails in
Wine x64 (tested on 6.0, 6.23, 7.0, 7.4, 7.5, 7.6, 7.9, 7.10, 7.11, 7.12) (and
in CrossOver 21.2.0 too)?
It fails to debug window - msiexec.exe fatal error.
By the way, x32 .msp file installation fails too in wine x32 prefix.
Could you fix it, please?
---
Remark:
Yes, this command:
wine msiexec /p vba71-kb2783832-x64.msp REINSTALL=ALL REINSTALLMODE=omus /qn
helps to _avoid_ a failed installation in Wine, but it's not right way. May be
becouse this "avoid-way" after we have critical falls in huge Software, that
needs this libraries installed.
In CrossOver 21.2.0, for example, this Software can't start right on VBA
initialization even with "avoid-way" command!
---
Working on this Software installation in Wine on linux about 4 months already,
sure that first problem is here.
Thanks and 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.
https://bugs.winehq.org/show_bug.cgi?id=49897
Bug ID: 49897
Summary: winetricks dotnet452 hangs
Product: Wine
Version: 5.18
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: dotnet, download, Installer, regression
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
Distribution: Gentoo
Created attachment 68254
--> https://bugs.winehq.org/attachment.cgi?id=68254
terminal output
While bug 49532 was fixed for dotnet40, dotnet452 still hangs for me.
--
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.