https://bugs.winehq.org/show_bug.cgi?id=54380
Bug ID: 54380
Summary: WINE debugger shows up at the start of every program.
Product: Wine
Version: 8.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: trivial
Priority: P2
Component: ntoskrnl
Assignee: wine-bugs(a)winehq.org
Reporter: tch(a)protonmail.com
Distribution: ---
When i run a program with WINE, the debugger window shows up and says
"Unhandled exception: unimplemented function ntoskrnl.exe.Ke386QueryIoAccessMap
called in 32-bit code (0x[address]).", then displays some other messages, then
disappears.
Then the program runs normally, but this did not happen before i upgraded to
WINE 8.0.
--
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=54166
Bug ID: 54166
Summary: Compilation fails with gcc 4.8.4 (error:
‘HTTP_STATUS_CONTINUE’ undeclared)
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: version2013(a)protonmail.com
Distribution: ---
Created attachment 73692
--> https://bugs.winehq.org/attachment.cgi?id=73692
log.txt
Compiling in 32 bit distro with:
compiler version 4.8.4
# gcc --version
glibc 2.19
# ldd --version
config line:
configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --with-x
--libdir=/usr/lib32 CFLAGS="-O2 -march=i686 -mtune=i686"
Compile error in wine-8.0-rc1
In function ‘cups_write_doc’
error: ‘HTTP_STATUS_CONTINUE’ undeclared (first use in this function)
--
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=54609
Bug ID: 54609
Summary: 32-bit LDAP Administrator crashes in internal Wine
function proxy_manager_destroy
Product: Wine
Version: 8.2
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: rpc
Assignee: wine-bugs(a)winehq.org
Reporter: alexhenrie24(a)gmail.com
Distribution: ---
Created attachment 74138
--> https://bugs.winehq.org/attachment.cgi?id=74138
WINEDEBUG=+ole
If I am reading the OLE trace correctly, the application:
1. Creates a proxy interface:
0110:trace:ole:proxy_manager_construct 01505048 created for OXID
2000000100, OID 3e
2. Sends the pointer to that interface to another thread:
0110:trace:ole:NdrBaseTypeMarshall value: 1505048
3. Releases and frees the interface:
0110:trace:ole:NdrInterfacePointerFree (04D4F594,01505048,1025B69C)
4. Receives the interface pointer on the other thread:
0100:trace:ole:NdrBaseTypeUnmarshall value: 1505048
5. Uses the interface on the other thread, despite it being freed:
0100:trace:ole:ClientIdentity_AddRef 01505048 - before 0
6. Releases and frees the interface again, which crashes:
0100:trace:ole:ClientIdentity_Release 01505048 - after 0
I don't understand how this works without crashing on Windows.
Here are all the traces that mention that interface pointer:
0110:trace:ole:proxy_manager_construct 01505048 created for OXID 2000000100,
OID 3e
0110:trace:ole:ClientIdentity_AddRef 01505048 - before 1
0110:trace:ole:ClientIdentity_Release 01505048 - after 1
0110:trace:ole:std_unmarshal_interface Successfully created proxy 01505048
0110:trace:ole:NdrBaseTypeMarshall value: 1505048
0110:trace:ole:NdrInterfacePointerFree (04D4F594,01505048,1025B69C)
0110:trace:ole:ClientIdentity_Release 01505048 - after 0
0100:trace:ole:NdrBaseTypeUnmarshall value: 1505048
0100:trace:ole:ClientIdentity_AddRef 01505048 - before 0
0100:trace:ole:ClientIdentity_Release 01505048 - after 0
The 64-bit version also crashes, but in a different way, see Bug 54606.
$ sha256sum ldapadmin-4.21.24429.0-x86-eng.msi
9d3e062b9c30d4bd73630b969414f65f969f0eafc5a3835f1ebb246c5c657d2a
--
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=54424
Bug ID: 54424
Summary: user32:edit - test_dbcs_WM_CHAR() fails on Windows in
mixed locales
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
user32:edit - test_dbcs_WM_CHAR() fails on Windows in mixed locales:
edit.c:3407: Test failed: W: got L"\02c6\00ea\201c", expected
L"\4e00\4e8c\4e09"
edit.c:3412: Test failed: W: got "?e\x81gn?O", expected "\x88\xea\x93\xf1\x8eO"
See https://test.winehq.org/data/patterns.html#user32:edit
The failures happen in the w10pro64-mx-MX test configuration. What's special
about it is that it uses a mix of locales:
SystemDefaultLCID 0411
UserDefaultLCID 040c
ThreadLocale 0411
SystemPreferredUILanguages 0412,0409
UserDefaultUILanguage 0412
ThreadUILanguage 0412
Country 231
ACP 932
The failures started happening with the commit that introduced the new tests:
commit cbe3a39b647e029df16faf1dcce2958f1ee418d0
Author: Akihiro Sagawa <sagawa.aki(a)gmail.com>
AuthorDate: Fri Jan 20 23:51:36 2023 +0900
user32/tests: Add DBCS WM_CHAR tests for edit control.
--
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=49772
Bug ID: 49772
Summary: Memory safety issues in widl
Product: Wine
Version: 5.16
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: tools
Assignee: wine-bugs(a)winehq.org
Reporter: kolan_n(a)mail.ru
Distribution: ---
I have tried to compile some type libraries missing in MinGW-w64 and Wine and
ReactOS SDKs too (more precisely, sapiddk.idl) into headers from the files in
Windows SDK (used Windows 10 SDK).
MinGW-w64 widl has crashed without producing any output, just left some files
with garbled filenames (looks like a zero terminator got missing in a C
string).
So I have built wine widl. It has also crashed, but at least produced some
meaningful output.
--
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=54074
Bug ID: 54074
Summary: ws2_32:sock - test_empty_recv() sometimes gets an
ERROR_IO_PENDING error in Wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: winsock
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
ws2_32:sock - test_empty_recv() sometimes gets an ERROR_IO_PENDING error in
Wine:
sock.c:12752: Test failed: got error 997
See https://test.winehq.org/data/patterns.html#ws2_32:sock
This happens about twice per month in the nightly WineTest runs but the first
known instance is on 2022-09-01 on debiant-wow32: there is no record of this
failure happening in the previous 3 months. So it is likely to be caused by
some commit in August.
This is also known to have happened in the GitLab CI environment which impacted
some merge requests (for instance MR!1561 and MR!1485).
--
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.
http://bugs.winehq.org/show_bug.cgi?id=9378
Summary: CM: Shock Force 'Could not initialize graphics display'
Product: Wine
Version: 0.9.43.
Platform: PC
URL: http://www.battlefront.com/products/cmsf/downloads.html
OS/Version: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: wine-directx
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: mailing_list(a)orange.nl
After starting Combat Mission: Shock Force Demo it stops with the message:
'Could not initialize graphics display. REQUIRED 1024x768, 32-bit
color'.
The terminal output doesn't provide any clues:
wine 'CM Shock Force DEMO.exe'
ALSA lib conf.c:3939:(snd_config_expand) Unknown parameters 0
ALSA lib control.c:910:(snd_ctl_open_noupdate) Invalid CTL default:0
err:alsa:ALSA_CheckSetVolume Could not find 'PCM Playback Volume' element
err:alsa:ALSA_CheckSetVolume Could not find 'PCM Playback Volume' element
fixme:wave:ALSA_AddCaptureDevice Add support for DSCapture
ALSA lib seq_hw.c:457:(snd_seq_hw_open) open /dev/snd/seq failed: No such file
or directory
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=49002
Bug ID: 49002
Summary: Free Horror Game "My Place" triggers
GL_INVALID_FRAMEBUFFER_OPERATION in wined3d
Product: Wine
Version: 5.4
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: dark.shadow4(a)web.de
Distribution: ---
Created attachment 66977
--> https://bugs.winehq.org/attachment.cgi?id=66977
Snipped from the log
At a certain section, the game spams this error, severely degrading the
performance.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=18889
Summary: Live Messenger 2008 fails to load - possible actctx
problem
Product: Wine
Version: 1.1.16
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: andras(a)csevego.net
Created an attachment (id=21730)
--> (http://bugs.winehq.org/attachment.cgi?id=21730)
+actctx,+relay log
Starting of installed (on windows) Msn 2009 wil result:
err:module:import_dll Library MSVCR80.dll (which is needed by
L"Z:\\media\\disk\\Program Files\\Windows Live\\Messenger\\msnmsgr.exe") not
found
err:module:LdrInitializeThunk Main exe initialization for
L"Z:\\media\\disk\\Program Files\\Windows Live\\Messenger\\msnmsgr.exe" failed,
status c0000135
Same load failure, when I manually install with wine (from msi packages)
MSVCRT 8.0 is installed, as shown attached +actctx,+relay log
I suspect here an Activation Context failure.
--
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.