https://bugs.winehq.org/show_bug.cgi?id=57187
Bug ID: 57187
Summary: System's audio device switches whenever an app
launches, then switches back again
Product: Wine
Version: 9.16
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: yaomtc(a)protonmail.com
Distribution: ---
This results in my PC's sound cutting out for a few seconds whenever I launch
something with Wine, and again if that thing is a launcher, launching something
else (e.g. Battle.net)
My primary audio output is via the onboard optical audio output (ALC1220
Digital). I also have HDMI output from my graphics card, and a USB audio
interface I only use for input. I have Pipewire installed on this Arch Linux
system with KDE Plasma.
--
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=57247
Bug ID: 57247
Summary: FL Studio is extremely sluggish
Product: Wine
Version: 9.18
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: dwmapi
Assignee: wine-bugs(a)winehq.org
Reporter: dark.shadow4(a)web.de
Distribution: ---
Download:
https://install.image-line.com/flstudio/flstudio_win64_24.1.1.4285.exe
Archived at
https://web.archive.org/web/20240821135437/https://install.image-line.com/f…
During installation you might encounter bug 57208 (doesn't happen for me
though).
After starting the program, open the "Keep it Simple" demo project.
The program uses a full core of CPU constantly. Trying to open the "FILE" menu
and moving the mouse over the entries, it hangs often for seconds at a time.
Same happens for most other actions.
As reported in bug 57240, the program seems to run smoothly for other users
though...
A performance measurement shows a thread constantly calling DwmFlush. I suspect
it might try to use DwmFlush as vsync-like operation. DwmFlush is currently a
stub, replacing it with a "Sleep(16)" makes the program work smoothly.
--
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=57241
Bug ID: 57241
Summary: Managed COM components fail to load outside of
application directory
Product: Wine
Version: 9.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: mscoree
Assignee: wine-bugs(a)winehq.org
Reporter: bob(a)paradoxlost.com
Distribution: ---
Managed assemblies are not loaded outside of the "current" directory due to a
failure to open the file using the CodeBase path.
https://gitlab.winehq.org/wine/wine/-/blob/master/dlls/mscoree/corruntimeho…
Here, the incorrect variable is passed to CreateFileW. It should be filename
instead of path.
--
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=57098
Bug ID: 57098
Summary: Battle.net does not start after upgrade to 9.16
Product: Wine
Version: 9.16
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: cmd
Assignee: wine-bugs(a)winehq.org
Reporter: sfjuocekr(a)gmail.com
Distribution: ---
Created attachment 76977
--> https://bugs.winehq.org/attachment.cgi?id=76977
log
Battle.net does not work with the latest wine-staging = 9.16
I had just updated wine from apt, the launcher starts but during login it opens
a command prompt with error message that closes and opens repeatedly.
I suppose this has something to do with the latest cmd.exe changes?
--
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=57137
Bug ID: 57137
Summary: endlocal changes CWD if pushd/popd are called before
Product: Wine
Version: 9.16
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: cmd
Assignee: wine-bugs(a)winehq.org
Reporter: huangqinjin(a)gmail.com
Distribution: ---
Run test.bat, got output
Z:\home
Z:\home\huangqinjin
Z:\home
test.bat:
@echo off
pushd "%~dp0.."
cd
popd
setlocal
cd
endlocal
cd
--
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=57244
Bug ID: 57244
Summary: Train capacity 300% 2 will crash after enable the
winedmo
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: l12436.tw(a)gmail.com
Distribution: ---
Created attachment 77161
--> https://bugs.winehq.org/attachment.cgi?id=77161
Detail log from Train capacity 300% 2
Also video regression due to winedmo.
Game will crash at the title video or gallery video
--
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=57148
Bug ID: 57148
Summary: ghidraRun.bat shows: Syntax error: unexpected IN
Product: Wine
Version: 9.16
Hardware: x86-64
OS: Linux
Status: NEW
Severity: minor
Priority: P2
Component: cmd
Assignee: wine-bugs(a)winehq.org
Reporter: bernhardu(a)mailbox.org
Distribution: ---
For starting up ghidra a batch file "ghidraRun.bat" can be used.
This shows the messages:
C:\ghidra_11.1.2_PUBLIC>:: Ghidra launch
Syntax error
Syntax error: unexpected IN
...
This is because there developers decided to use %# as iterator variable.
Indeed native can handle almost all ascii character
above space until tilde except these: "&,;<=>^|
The application starts up successfully because this should just detect
if it got started via a doubleclick or from a console window,
so this is just a minor issue.
https://github.com/NationalSecurityAgency/ghidra/blob/184180d54dbdf3db3c030…
--
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=57224
Bug ID: 57224
Summary: Strange Behavior with >64 Processing Cores
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: atericparker(a)gmail.com
Distribution: ---
Created attachment 77143
--> https://bugs.winehq.org/attachment.cgi?id=77143
Compiled Microsoft Sample code to test API
I've been spending the last few weeks trying to figre out why Photoshop crashes
with >64 threads, unless one disables multithreading outright by deleting
MultiProcessor Support.pbx (which is actually a dll).
After disassembling the pbx file, and debugging Photoshop with x64dbg (under
wine) I determine that the crash occurs briefly after calling
GetLogicalProcessorInformation from Kernel32.dll. The crash occurs after the
return of the number of logical processors, so it's not the actual function
crashing, just that it is returning a value that causes an issue.
I then proceeded to test the API with this sampel code (I attached a compiled
version)
https://learn.microsoft.com/en-us/windows/win32/api/sysinfoapi/nf-sysinfoap…
, and compare the output across systems. On Windows (& wine <64 CPUs), the
number of logical processors works as expected, as does cores.
When we cross the 64 CPU barrier, something strange happens (which I assume
causes the crash). We get 65 cores and 64 threads, which is impossible, from
stepping through the debugger, I confirm that Photoshop also gets a 65 count.
GetLogicalProcessorInformation results:
Number of NUMA nodes: 1
Number of physical processor packages: 1
Number of processor cores: 65
Number of logical processors: 64
Number of processor L1/L2/L3 caches: 130/65/9
Any ideas what's going wrong here? I understand that wine doesn't support >64
threads, but it seems like an off by 1 error.
--
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=57173
Bug ID: 57173
Summary: Wine-dev 9.17 does not allow drag-and-drop of files
into LTspice
Product: Wine
Version: 9.17
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: drprimeevil.myopera(a)gmail.com
Distribution: ---
Cannot drag-and-drop schematics files (or any relevant files) into LTspice
24.0.12 using Wine 9.17 (development version).
Under Wine 9.16 it used to work - all be it after several tries. It used to
either work properly or come up with a message box saying, "no error" but no
file in the application. After another attempt it would succeed or sometimes a
few attempts - each unsuccessful attempt coming up with the message box. But
ultimately it would succeed.
Now, there would be no file, no message box. Just nothing.
--
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=51386
Bug ID: 51386
Summary: ln.exe needs KERNEL32.dll.FindFirstFileNameW
Product: Wine
Version: 6.12
Hardware: x86-64
URL: https://web.archive.org/web/20210530064017/https://sch
inagl.priv.at/nt/ln/ln.html
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: awineuser(a)mail.com
Distribution: Ubuntu
ln.exe, a command line utility that works with hard links and symbolic links,
can crash during a "deloreon copy" (incremental backup). Specifically, the
command used was this:
ln --backup --unroll --1023safe --progress --delorean <source directory>
<previous backup dir> <new backup dir>
When it crashes, the terminal output says:
wine: Call from 7BC2980A to unimplemented function
KERNEL32.dll.FindFirstFileNameW, aborting
Sometimes the command completes without crashing, so apparently it doesn't
always call this function?
Note: the 32-bit version of ln.exe was used. I haven't tested the 64-bit
version.
--
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.