https://bugs.winehq.org/show_bug.cgi?id=54317
Bug ID: 54317
Summary: Change to exec_wineloader made wine not start at all
Product: Wine
Version: 8.0-rc4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: hibbsncc1701(a)gmail.com
Distribution: ---
Attempting to start wine with a pre-existing prefix results in a failure to
load ntdll / kernel32. With messages like
"wine: could not load kernel32.dll, status c0000135"
and
002c:err:module:load_wow64_ntdll failed to load
L"\\??\\C:\\windows\\system32\\ntdll.dll" error 4000000e
wine: Unhandled page fault on execute access to 00000000 at address 00000000
(thread 002c), starting debugger...
being printed in the console.
Wine then attempts to start winedbg only to get stuck in a forkbomb. Where
winedbg won't start, triggering an exception, which will cause another attempt
to start winedbg. At a rate of about 4-5 attempts a second. Attempting to
ctrl-c it doesn't work, and requires manually terminating all of wine's
processes. (Of which are numerous as wine will also attempt to start
conhost.exe for each winedbg it attempts to load. None of which will terminate
on their own.)
Attempting to start wine with a fresh prefix results in an incomplete prefix
directory. (Only the dosdevices / windows directories, and registry hives are
present in the prefix. Of those windows is empty save for the syswow64 and
system32 directories of which both are completely empty.) Attempting to start
that prefix again causes the same winedbg behavior as above.
Performing a bisect revealed:
$ git bisect bad
d45de318748639cfd1e80a976b39f5e19213990f is the first bad commit
commit d45de318748639cfd1e80a976b39f5e19213990f
Author: Alexandre Julliard <julliard(a)winehq.org>
Date: Tue Nov 22 12:08:19 2022 +0100
ntdll: Always set WINELOADER variable to the current loader name.
dlls/ntdll/unix/env.c | 3 +++
dlls/ntdll/unix/loader.c | 48 +++++++++++++++++++++---------------------------
2 files changed, 24 insertions(+), 27 deletions(-)
Reverting d45de318748639cfd1e80a976b39f5e19213990f fixed the issue on my
system.
--
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=45328
Bug ID: 45328
Summary: Unusable GUI for ElsterFormular 19.5
Product: Wine
Version: 3.10
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: Markus.Elfring(a)web.de
Distribution: ---
It would be nice if I could use the application “ElsterFormular 19.5
(2018-06-14)” together with the software “Wine 3.10-820.1” finally.
https://www.elster.de/eportal/infoseite/elsterformularhttps://appdb.winehq.org/objectManager.php?sClass=application&iId=1925
elfring@Sonne:~> wine C:\\windows\\command\\start.exe /Unix
/home/elfring/.wine/dosdevices/c:/users/elfring/Start\
Menu/Programs/ElsterFormular/ElsterFormular.lnk
0009:fixme:exec:SHELL_execute flags ignored: 0x00000100
0009:fixme:exec:SHELL_execute flags ignored: 0x00004100
elfring@Sonne:~> 0036:fixme:file:FindFirstFileExW flags not implemented
0x00000002
0036:fixme:file:FindFirstFileExW flags not implemented 0x00000002
0036:fixme:msvcrt:type_info_name_internal_method type_info_node parameter
ignored
…
Its graphical user interface does not respond to mouse clicks so far.
--
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=41102
Bug ID: 41102
Summary: Alan Wake's American Nightmare crashes at launch
randomly with 'm->state == STATE_PASSIVE'
Product: Wine
Version: 1.9.16
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: winepulse.drv
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
CC: aeikum(a)codeweavers.com
Distribution: ---
Crashes very randomly, so hard to reproduce.
Assertion 'm->state == STATE_PASSIVE' failed at pulse/mainloop.c:787, function
pa_mainloop_prepare(). Aborting.
wine: Assertion failed at address 0xf779ad49 (thread 0028), starting
debugger...
Unhandled exception: assertion failed in 32-bit code (0xf779ad49).
Backtrace:
=>0 0xf779ad49 __kernel_vsyscall+0x9() in [vdso].so (0x7c1bd2e8)
1 0xf73d95c9 gsignal+0x38() in libc.so.6 (0x7c1bd2e8)
2 0xf73daca7 abort+0x156() in libc.so.6 (0x7c1bd2e8)
3 0x7a9e9e47 pa_mainloop_prepare+0x286() in libpulse.so.0 (0x7c1bd2e8)
4 0x7a9ea923 pa_mainloop_iterate+0x32() in libpulse.so.0 (0x04a0dc98)
5 0x7aa512b3 pulse_test_connect+0x182()
[/wine/dlls/winepulse.drv/mmdevdrv.c:566] in winepulse (0x04a0dc98)
6 0x7aa58590 AUDDRV_GetPriority+0x2f()
[/wine/dlls/winepulse.drv/mmdevdrv.c:947] in winepulse (0x04a0dcc8)
7 0x7b8199bf init_driver+0x25e() [/wine/dlls/mmdevapi/main.c:103] in mmdevapi
(0x04a0e1c8)
8 0x7b81a21c DllGetClassObject+0x3b(rclsid=<couldn't compute location>,
riid=<couldn't compute location>, ppv=<couldn't compute location>)
[/wine/dlls/mmdevapi/main.c:282] in mmdevapi (0x04a0e1f8)
9 0x7e95fc1c apartment_getclassobject+0x11b(apt=<is not available>,
dllpath=<is not available>, apartment_threaded=<is not available>, rclsid=<is
not available>, riid=<is not available>, ppv=<is not available>)
[/wine/dlls/ole32/compobj.c:1372] in ole32 (0x04a0e268)
10 0x7e962bd5 get_inproc_class_object+0x114(apt=<is not available>,
regdata=<is not available>, rclsid=<is not available>, riid=<is not available>,
hostifnecessary=<is not available>, ppv=<is not available>)
[/wine/dlls/ole32/compobj.c:2930] in ole32 (0x04a0e4c8)
11 0x7e965565 CoGetClassObject+0x50f(rclsid=<is not available>,
dwClsContext=<is not available>, pServerInfo=<is not available>, iid=<is not
available>, ppv=<is not available>) [/wine/dlls/ole32/compobj.c:3068] in ole32
(0x04a0e578)
12 0x7e966be1 CoCreateInstanceEx+0x1db(rclsid=<is not available>,
pUnkOuter=<is not available>, dwClsContext=<is not available>, pServerInfo=<is
not available>, cmq=<is not available>, pResults=<is not available>)
[/wine/dlls/ole32/compobj.c:3305] in ole32 (0x04a0e5f8)
13 0x7e9670dd CoCreateInstance+0x67(rclsid=<is not available>, pUnkOuter=<is
not available>, dwClsContext=<is not available>, iid=<is not available>,
ppv=<is not available>) [/wine/dlls/ole32/compobj.c:3201] in ole32 (0x04a0e668)
14 0x01e8347b in fmodex (+0x347a) (0x04a0e694)
15 0x01f07e45 in fmodex (+0x87e44) (0x04a0e6bc)
16 0x01f07f7a in fmodex (+0x87f79) (0x04a0e6d4)
17 0x01f080b8 in fmodex (+0x880b7) (0x04a0e70c)
18 0x01ea2e74 in fmodex (+0x22e73) (0x04a0e728)
19 0x01e569b4 in snd_w32_f (+0x69b3) (0x04a0e900)
20 0x01e573fa in snd_w32_f (+0x73f9) (0x04a0e928)
21 0x01e57a9c in snd_w32_f (+0x7a9b) (0x04a0e948)
22 0x0042f4e4 in alan_wakes_american_nightmare (+0x2f4e3) (0x04a0e990)
23 0x0042fb0b in alan_wakes_american_nightmare (+0x2fb0a) (0x04a0e9c4)
24 0x006eded0 in alan_wakes_american_nightmare (+0x2edecf) (0x04a0e9f4)
25 0x00d99f02 in rl_w32_f (+0x59f01) (0x04a0ea08)
26 0x7bc7d8ac call_thread_func_wrapper+0xb() in ntdll (0x04a0ea18)
27 0x7bc80669 call_thread_func+0xa8(entry=0xd42b8a, arg=0x399d2a0,
frame=0x4a0eb18) [/wine/dlls/ntdll/signal_i386.c:2759] in ntdll (0x04a0eaf8)
28 0x7bc7d88a call_thread_entry_point+0x11() in ntdll (0x04a0eb18)
29 0x7bc88073 start_thread+0xa2(info=0x7ffd0fb8)
[/wine/dlls/ntdll/thread.c:453] in ntdll (0x04a0f368)
PulseAudio 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=54341
Bug ID: 54341
Summary: dotnet-dump data collection or some other backtrace
for dotnet applications?
Product: Wine
Version: 7.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mjevans1983(a)gmail.com
Distribution: ---
Created attachment 73910
--> https://bugs.winehq.org/attachment.cgi?id=73910
winedbg.exe dump during the livelock
I'm trying to figure out why a game (Cosmoteer again) freezes when
multi-threading is enabled. The current work around is to run it in 'single
core' ( --cores 1 ) mode, but obviously the performance is quite inferior for
an application intended to run on multiple cores. On my system when it's
briefly working it uses between 300 and 500% of a core (so 3-5 physical cores
on a 4c8t system).
I need to collect more data to isolate if it's an issue with the game or with
wine, and I don't even know where to begin looking for Wine data since I can't
get a backtrace from any tools.
gdb doesn't know about applications that run through wine.
winedbg doesn't appear to understand dotnet managed applications (attachment)
I tried to run dotnet-dump but the tool installed in Linux doesn't locate any
applications that it can interact with, while the 64-bit (matches the program)
version of the tool inside wine appears to want a full dotnet install.
https://github.com/dotnet/diagnostics/blob/main/documentation/single-file-t…
So much for a single file tool ~.~
Is there some way I could collect more data without help from the program's
creator? I've already suggested they please trap SIGTERM, SIGINT, SIGQUIT, and
SIGHUP but I don't even know if that will work for an application using wine.
https://steamcommunity.com/app/799600/discussions/1/3762228045904230736/
--
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=52538
Bug ID: 52538
Summary: Regression: Yamaha Expansion Manager crashes
Product: Wine
Version: 7.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: joseskvolpe(a)gmail.com
Distribution: ---
I found out this application has got a regression on a older regression
Based on the test results history, it has got a platinum rating in Wine 6.0,
but the application crashes on the start-up on Wine 7.1 so it's rating is now
Garbage.
I tested it on a self-compiled Wine 6.0.2, the application works well on a
WoW64 prefix all-trial, but crashes on a 32-Bits prefix. I've downloaded newer
Wine binaries from Arch's packages archive
(https://archive.archlinux.org/packages/w/wine/) and tested the application
multiple-times, it works until Wine 6.9, older versions works but crashes
sometimes, so i've to try it 5 times to be sure it's not working. The
application won't work on Wine 6.9 no matter how much time you try it.
But i'm afraid i couldn't find the bad commit, there's something very weird on
this issue, let me explain.
That was my methodology for regression testing it:
1 - Erase the wineprefix
2 - Make the bisection (bisect start, bisect skip, bisect good or bisect bad)
3 - WoW64 Wine compile (wine-64 build, then wine-32 build)
4 - Create a new WoW64 wineprefix
5 - Try application multiple times, if it succeeds then it's bisect good, if it
crashes after trying it over 5 times, then it's bisect bad
However, the application could always succeed after compiling Wine before the
5th try, until the last bisection.
I tried again bisecting Wine 6.9 and Wine 6.10. The application were crashing
on both Wine 6.9 and Wine 6.10 from Arch's binary archive, but it could succeed
if i compile them.
I'd the same issue, although the application could indeed crash sometimes (wich
also occurs on older Wine versions), it were always succeeding before the 5th
try, so i couldn't find what was the commit that caused the regression.
¿Maybe is that a issue from who's compiling Wine for Arch?
¿Should i compile Wine 7.1 and try the application?
I planned to become a maintainer for the application only to add a proper
description and then leave, but now i'll stay maintaining this application for
a while until we can figure it out.
¿Can you devs reproduce the crash on other distributions?
Download: https://tw.yamaha.com/zh/support/updates/yem_win_v260.html
SHA1: b6255d5371679554b72f29a00008578438a1bfe6
Procedure:
1 - Run "Expansion Manager.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.
https://bugs.winehq.org/show_bug.cgi?id=52145
Bug ID: 52145
Summary: 2gis 3.16.3: error after exit
Product: Wine
Version: 6.0.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: v.yuzbekov(a)yandex.ru
Distribution: ---
Created attachment 71192
--> https://bugs.winehq.org/attachment.cgi?id=71192
backtrace
An error occurs after the ad window is displayed while exiting the 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.
https://bugs.winehq.org/show_bug.cgi?id=51135
Bug ID: 51135
Summary: Arturia Pigments 3 crashes when mousing over the
volume control
Product: Wine
Version: 6.8
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sgarman(a)zenlinux.com
Distribution: ---
Created attachment 70000
--> https://bugs.winehq.org/attachment.cgi?id=70000
Arturia Pigments 3 crash backtrace
Pigments 3 is a VST synthesizer plugin used in music production. It can be
found at:
https://www.arturia.com/products/analog-classics/pigments#en
and it installs successfully in Wine via Arturia's Software Center, which is
available at the top of this list:
https://www.arturia.com/support/downloads&manuals
Pigments seems to be working well, with one significant flaw - if you mouse
over the volume control knob icon (in the upper right corner of the UI), the
app freezes/crashes. I believe this is the only thing preventing this synth
plugin from working flawlessly.
I'll attach a backtrace of the crash report. I'm running the latest Wine
Staging (6.8) on an Ubuntu 20.04 system with kernel 5.9.16-050916-generic from
Ubuntu's kernel PPA.
--
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=54259
Bug ID: 54259
Summary: Firefox displays virus for wine-8.0-rc2.tar.xz
Product: WineHQ Bugzilla
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: bugzilla-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: juergen(a)luers-net.de
CC: austinenglish(a)gmail.com
Distribution: ---
Downloaded at https://www.winehq.org/news/ from "The source is available now."
Firefox shows that the file contains a virus or malware.
Downloading from https://dl.winehq.org/wine/source/8.0/wine-8.0-rc2.tar.xz does
not display that message. Both files differ.
Firefox is version 108.0.1 (64-Bit) under Ubuntu 22.04 64bit.
--
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=50822
Bug ID: 50822
Summary: Sniper: Ghost Warrior 2 has rendering glitch in DX9
mode with OpenGL renderer
Product: Wine
Version: 6.4
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
Distribution: ---
Created attachment 69640
--> https://bugs.winehq.org/attachment.cgi?id=69640
example
wine-6.4-118-g2828d0820a1
--
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=50136
Bug ID: 50136
Summary: allow to disable wine's vulkan loader/driver
Product: Wine
Version: 5.21
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: winevulkan
Assignee: wine-bugs(a)winehq.org
Reporter: xantares09(a)hotmail.com
Distribution: ---
I'm trying to run mesa's software vulkan renderer driver with wine.
This means I want to use vulkan's icd loader and mesa's renderer libs I built
(outside of wine):
libvulkan-1.dll
libvulkan_lvp.dll
Unfortunately, building wine with --disable-vulkan does not seem to disable its
loader, it only disables the driver:
$ VK_ICD_FILENAMES=lvp_icd.x86_64.json wine vkcubepp.exe
0064:err:vulkan:get_vulkan_driver Wine was built without Vulkan support.
Is there a way to disable the loader too ?
--
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.