https://bugs.winehq.org/show_bug.cgi?id=53553
Bug ID: 53553
Summary: F.E.A.R. won't work with DSOAL surround sound
restoration DLL replacement
Product: Wine
Version: 7.14
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: dsound
Assignee: wine-bugs(a)winehq.org
Reporter: mr.matt.eastwood(a)gmx.de
Distribution: ---
Steps to Reproduce:
1. Install F.E.A.R. (e.g., "Fear Platinum" from GOG)
2. Get DSOAL from https://github.com/kcat/dsoal and compile dsound.dll
3. Get latest OpenAL-Soft bin from https://openal-soft.org/
4. Unzip soft_oal.dll from its bin\Win32 directory
5. Rename that file to dsoal-aldrv.dll
6. Place both dsoal-aldrv.dll and DSOAL's dsound.dll in same directory as
FEAR.exe
7. Run game
8. Enter sound menu
Expected Results:
When running F.E.A.R. with the DLL replacement DSOAL for surround sound
restoration, the advanced sound options "Enable HW mixing", "Enable EAX 2.0"
and "Enable EAX Advanced HD" should be available in the sound menu and surround
sound including EAX effects should work.
Current Results:
The sound options remain greyed-out.
Observations:
F.E.A.R. won't load dsound.dll from anywhere but syswow64. If one places the
DSOAL dsound.dll there (replacing Wine's own), and then sets dsound.dll to
"native" e.g. through winecfg, everything works. Screenshot:
If one sets dsound.dll to "native" e.g. through winecfg and then loads the game
without replacing Wine's dsound.dll in syswow64 (but with the DSOAL files in
the F.E.A.R. folder): "Failed to initialize sound driver 'SndDrv.dll' on
startup. Screenshot: https://paste.pics/I4DO0. No sound during game or menus,
only during intro movie. Available sound options: https://paste.pics/I4DOD
--
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=49915
Bug ID: 49915
Summary: can not register COM server
Product: Wine
Version: 5.18
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ysong2180(a)yahoo.com
Distribution: ---
Created attachment 68286
--> https://bugs.winehq.org/attachment.cgi?id=68286
two log files. one is the winecfg log. The other one is the application log
I tried to install an windows application on Ubuntu 20.04. The installer can
run and install files. But it fails at the end when it tries to register COM
servers. It is a win32 application. I used winecfg to create a win32
wineprefix and used the win32 wineprefix to start the installer.
--
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=54677
Bug ID: 54677
Summary: Wine cannot find tools in tool dir when cross
compiling
Product: Wine
Version: 8.3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: tools
Assignee: wine-bugs(a)winehq.org
Reporter: ale.schenberg(a)yandex.com
Distribution: ---
Created attachment 74193
--> https://bugs.winehq.org/attachment.cgi?id=74193
config.log
Hello. When trying to cross build wine, configure's execution breaks due to it
to not find wine tools in the tools dir.
My building command:
LDFLAGS=-Wl,--dynamic-link=/usr/lib32/ld-2.17.so ./configure
--host=i686-gnu-linux --with-wine-tools=tools/
I attached config.log, although it appears to contain no useful information.
The bug applies to wine 8.3 and any other wine version that I tested (such as
1.9)
I think its worthy to mention that cross build it is more a necessity imposed
by the configure script than my wish. As I am forced to pass
"LDFLAGS=-Wl,--dynamic-link=/usr/lib32/ld-2.17.so" to configure (if not, the
building won't be able to run any auxiliary 32bit components, such as makedep,
unless I statically build them), configure demands the use of host, and then of
--with-wine-tools
--
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=47000
Bug ID: 47000
Summary: Make WineHQ available as flatpak in Flathub
Product: Packaging
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-packages
Assignee: wine-bugs(a)winehq.org
Reporter: yousifjkadom(a)yahoo.com
CC: michael(a)fds-team.de, sebastian(a)fds-team.de
Distribution: ---
Hi.
I would like, here, to suggest to make WineHQ available as flatpak in Flathub.
This will be very useful since flatpak is secure & sandboxed, so user will be a
way from infect heir/his PC by a virus or spywar. If flatpak Wine run a virus,
then it will be like if Wine sandboxed by firejail run such virus.
Moreover, flatpak can minimize time & efforts in packaging because it is a
generic package working in many Linux distro regardless OS version.
Also, Wine contain huge number of 32 bit packages that are, mostly, not needed
by any other application.
--
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=54674
Bug ID: 54674
Summary: Add Flatpak to Download page
Product: WineHQ.org
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: www-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: peter.eszlari(a)gmail.com
Distribution: ---
Since February 2022 Wine has been available as a Flatpak.
To try it:
0. ($ apt install flatpak)
1. $ flatpak remote-add flathub https://flathub.org/repo/flathub.flatpakrepo
2. $ flatpak install org.winehq.Wine
3. $ flatpak run org.winehq.Wine prog.exe
build manifest source: https://github.com/flathub/org.winehq.Wine
I think it would make sense to add this to list of binary packages on:
https://wiki.winehq.org/Download
(Note: Wine cannot be found on the Flathub web interface at
https://flathub.org, because only GUI apps are listed there, not CLI apps.)
--
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=37640
Bug ID: 37640
Summary: Opening Windroy and it crashes.
Product: Wine
Version: 1.6.2
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fholiveira1(a)hotmail.com
Distribution: ---
Created attachment 50094
--> https://bugs.winehq.org/attachment.cgi?id=50094
Extract from Wine report of bug.
I was trying to open Windroy and it crashes. The system open a bug report,
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=54508
Bug ID: 54508
Summary: psapi:psapi_main - The 64-bit
test_EnumProcessModulesEx() gets unexpected snapshot
counts on Windows 7 and 11
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: psapi
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
psapi:psapi_main - The 64-bit test_EnumProcessModulesEx() gets unexpected
snapshot counts on Windows 7 and 11:
w7pro64:
psapi_main.c:483: Test failed: pcs-6432: Wrong count 23 in C:\Windows\SysWOW64
psapi_main.c:488: Test failed: pcs-6432: Wrong count 2 in C:\Windows\system32
w11pro64:
psapi_main.c:488: Test failed: pcs-6432: Wrong count 0 in C:\Windows\system32
See https://test.winehq.org/data/patterns.html#psapi:psapi_main
These failures don't happen on Windows 8 to Windows 10!
These tests and failures were introduced in the following commit:
commit e38455a2181ab5ce0bf842f2c9a638b3ee9b538c
Author: Eric Pouech <eric.pouech(a)gmail.com>
AuthorDate: Tue Feb 14 11:06:57 2023 +0100
psapi/tests: Test directory of enumerated loaded modules.
Showing that Wine incorrectly reports, for a Wow64 process, the system
DLLs from within the wow64 directory while they should be from system32.
Signed-off-by: Eric Pouech <eric.pouech(a)gmail.com>
--
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=54662
Bug ID: 54662
Summary: The winscard tests are not run on the TestBot Wine VMs
Product: Wine-Testbot
Version: unspecified
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: unknown
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
Distribution: ---
The winscard tests are not run on the TestBot Wine VMs:
winscard missing
See the newtb-debian11-*, newtb-debian11b-* and newtb-debiant-* Linux results
on:
http://winetest.dolphin/data/tests/winscard:winscard.html
The reason is that the VMs are missing the libpcsclite libraries and maybe
other infrastructure needed to actually run the tests: if one just installs the
libraries the tests immediately get an SCARD_E_NO_SERVICE error and bail out:
can't establish context, make sure pcscd is running
--
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=54658
Bug ID: 54658
Summary: gdi32:driver -
test_D3DKMTCheckVidPnExclusiveOwnership() sometimes
fails due to occlusion error on Windows 8
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: gdi32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
gdi32:driver - test_D3DKMTCheckVidPnExclusiveOwnership() sometimes fails due to
INVALID_VIDEO_PRESENT_SOURCE error on Windows 8:
driver.c:461: Test failed: Got unexpected return code 0xc01e0006 at test 0.
driver.c:461: Test failed: Got unexpected return code 0xc01e0006 at test 1.
driver.c:461: Test failed: Got unexpected return code 0xc01e0006 at test 2.
[... same for tests 3 -> 58 ...]
driver.c:461: Test failed: Got unexpected return code 0xc01e0006 at test 59.
driver.c:481: Test failed: Got unexpected return code 0xc01e0304.
driver.c:505: Test failed: Got unexpected return code 0xc01e0006.
driver.c:556: Test failed: Got unexpected return code 0xc01e0006 at test 0.
[... same for tests 1 -> 16 ...]
driver.c:523: Test failed: Got unexpected return code 0xc01e0304 at test 17.
[... more code 0xc01e0304 errors ...]
driver.c:754: Test failed: Got unexpected return code 0xc01e0304.
driver.c:766: Test failed: Got unexpected return code 0.
[... more code 0 errors ...]
driver.c:785: Test failed: Got unexpected return code 0.
driver.c:807: Test failed: Got unexpected return code 0xc01e0006.
See https://test.winehq.org/data/patterns.html#gdi32:driver
Where:
0xc01e0006 == STATUS_GRAPHICS_PRESENT_OCCLUDED
0xc01e0304 == STATUS_GRAPHICS_INVALID_VIDEO_PRESENT_SOURCE
The oldest known instance was on 2023-12-09 and there has been about one per
month since:
* 2022-12-09 on w864 64-bit
* 2023-02-06 on w864 64-bit
* 2023-03-09 on w864 64-bit
--
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.