https://bugs.winehq.org/show_bug.cgi?id=56330
Bug ID: 56330
Summary: Regression: Vietcong: Audio cuts off and repeats
Product: Wine
Version: 9.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sa(a)whiz.se
Distribution: ---
The game Vietcong suffers from audio cutting of too early and/or repeating
several times. This is a regression introduced during Wine 5.x development but
still an issue with current git. Bisecting leads to this commit:
a10824a03cb7ad1a2a1987433c5ad832dcdf6962 is the first bad commit
commit a10824a03cb7ad1a2a1987433c5ad832dcdf6962
Author: Andrew Eikum <aeikum(a)codeweavers.com>
Date: Mon Aug 17 10:38:18 2020 -0500
winepulse: Don't rely on pulseaudio callbacks for timing.
Contains contributions from Mark Harmstone and Zhiyi Zhang.
Some devices, especially USB devices, have very irregular timing or
very long periods. Some Windows applications (The Witcher 3) are built
to expect regular, short period times, and so would underrun when the
device timing didn't match their expectations. This patch decouples
the Windows-side timing from the OS-side timing so we can meet those
applications' requirements.
Signed-off-by: Andrew Eikum <aeikum(a)codeweavers.com>
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
dlls/winepulse.drv/mmdevdrv.c | 613 +++++++++++++++++++-----------------------
1 file changed, 279 insertions(+), 334 deletions(-)
To reproduce, either patch Wine to include the change from #39057 or use the
fan-made patch VCStarter (1.7 BETA) from
http://www.vietcong.info/portal/forum/viewthread.php?thread_id=899
The sound issue is somewhat noticeable with the music in the main menu but very
noticeable if you listen to the drill sergeant in the tutorial levels. Select
"Single player" -> "Tutorial" -> "Drill camp 1".
There's a demo available but it does not exhibit the 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=56478
Bug ID: 56478
Summary: Requesting sub HD fullscreen resolutions breaks
applications/games on Apple Silicon
Product: Wine
Version: 9.5
Hardware: aarch64
OS: MacOS
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: winemac.drv
Assignee: wine-bugs(a)winehq.org
Reporter: ammoniak-molar-0r(a)icloud.com
Apple Silicon equipped Macs do not support "legacy" low (virtual?) display
resolutions anymore. Due to this several old Windows games running through wine
are broken, even though they run perfectly well otherwise.
Resolutions like 800x600px and lower are definitely effected, though I think
this applies to anything below 1024x768px.
A possible but undesired workaround is falling back the legacy X11 (XQuartz)
environment and its virtual desktop mode or using windows side tools which
enforce executables to run in windowed mode (like Dxwnd).
To my knowledge implementing something like the before mentioned virtual
desktop mode isn't feasible on macOS as child windows aren't supported.
Therefor I propose the solution, that the winemac.drv should ignore
wine/windows API "fullscreen calls", if the desired resolution is below
1024x768, when running on Apple Silicon. While this might break wine's
philosophy regarding windows function parity it would allow older software to
"just work" again without any manual workarounds.
An effected windows game would be "Colin McRae Rally 2005" which got a Demo
available. Further information, documentation and links regarding this issue
can be found here:
https://github.com/Gcenx/WineskinServer/issues/530#issuecomment-2016763641
Best,
Rastafabisch
--
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=41930
Bug ID: 41930
Summary: Civilization III Complete shows black terrain (Wine
compiled with OSMesa support)
Product: Wine
Version: 1.7.38
Hardware: x86
OS: Linux
Status: NEW
Keywords: regression
Severity: normal
Priority: P2
Component: gdi32
Assignee: wine-bugs(a)winehq.org
Reporter: gyebro69(a)gmail.com
CC: michael(a)fds-team.de
Regression SHA1: e618ab65ed5b623785c58ea5ece6e39895d43063
Distribution: ---
Created attachment 56311
--> https://bugs.winehq.org/attachment.cgi?id=56311
screenshot
This is one of the few games that I know of which makes some use of OpenGl in
bitmaps. When Wine was compiled with OSMesa support, tiles containing terrain
turn black as soon as I launch a game.
Reproduced with Nvidia binary drivers 375.20 and nouveau/mesa.
I tried Civilization III Complete (both the Steam and the GOG.com versions have
this bug).
Terminal output:
fixme:x11drv:X11DRV_desktop_SetCurrentMode Cannot change screen BPP from 32 to
16
err:ole:CoGetClassObject class {5959df60-2911-11d1-b049-0020af30269a} not
registered
err:ole:CoGetClassObject no class object {5959df60-2911-11d1-b049-0020af30269a}
could be created for context 0x1
Reverting the following patch on top of git fixes the problem:
commit e618ab65ed5b623785c58ea5ece6e39895d43063
Author: Michael Müller <michael(a)fds-team.de>
Date: Tue Feb 3 11:07:38 2015 +0100
gdi32: Fix arguments for OSMesaMakeCurrent when using 16 bit formats.
Please let me know if you need debug logs.
wine-1.9.24-105-g1d3b944
Fedora 24 x86_64
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GT 730/PCIe/SSE2
OpenGL core profile version string: 4.5.0 NVIDIA 375.20
Installed packages:
mesa-libOSMesa.i686 13.1.0-0.12.git95ddb37.fc24
mesa-libOSMesa.x86_64 13.1.0-0.12.git95ddb37.fc24
mesa-libOSMesa-devel.i686 13.1.0-0.12.git95ddb37.fc24
mesa-libOSMesa-devel.x86_64 13.1.0-0.12.git95ddb37.fc24
--
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=57537
Bug ID: 57537
Summary: Steuersparerklärung 2024 fails to install
Product: Wine
Version: 9.22
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dark.shadow4(a)web.de
Distribution: ---
Found while testing a report from the forums:
https://forum.winehq.org/viewtopic.php?t=39775
Ran in a clean WINEPREFIX, used trial version and express installation. It
gives a messagebox with
> Die Installation von >>Steuersparerklärung 2024<< konnte nicht durchgeführt werden! Prüfen Sie bitte, ob die notwendigen Installationsvoraussetzungen erfüllt sind
Translated:
The installation of >>Steuersparerklärung 2024<< could not be completed! Please
check whether the necessary installation requirements are met
--
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=49167
Bug ID: 49167
Summary: Wine staging 5.8 not available on macos download page
Product: Wine-staging
Version: 5.8
Hardware: x86
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: rmkk(a)atlas.cz
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Please check the reason
--
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=57513
Bug ID: 57513
Summary: Keyboard input is unavailable in Russian keyboard
layout in putty
Product: Wine
Version: 9.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: unxed(a)mail.ru
Distribution: ---
Tried version
https://the.earth.li/~sgtatham/putty/0.82/w64/putty.exe
~$ wine --version
wine-9.0 (Ubuntu 9.0~repack-4build3)
Mint 22 x64 Cinnamon, x11
Input in English keyboard layout works ok.
--
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=57600
Bug ID: 57600
Summary: Application not showing console output
Product: Wine
Version: 10.0-rc3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: angel.narvaez(a)civiceye.com
Distribution: ---
Created attachment 77715
--> https://bugs.winehq.org/attachment.cgi?id=77715
wine8 vs wine9
I'm running into an issue where an application that can be started from
explorer.exe or cmd.exe is not showing the console output to the unix console.
The "buggy" behavior is present in wine v9, but wine v8 shows the console
output just fine. I believe the related change is in this commit:
https://gitlab.winehq.org/wine/wine/-/commit/4b63e888945b8ada2ddc043e435b93…
In the commit, it is stated that this behavior can be achieved by starting the
app with "./wine app | cat", however that does not seem to be working with wine
or wineconsole (Please see attachments)
When using WINEDEBUG=+console, I can see the application interacting and
writing to the windows console, however nothing is shown on the screen. I need
guidance on this issue.
--
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=57837
Bug ID: 57837
Summary: game controller unusable
Product: Wine
Version: 10.1
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: amie1972(a)163.com
Distribution: ---
The game freezes after turning on the game controller。
The previous version did not have this problem.
Since this operation process directly caused the game to freeze, I cannot
provide screenshots or even logs.
--
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=10522
Summary: endless WM_PAINT loop bug (update regions, queue paint
count)
Product: Wine
Version: CVS/GIT
Platform: PC
URL: http://www.microsoft.com/whdc/devtools/debugging/install
x86.mspx
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: wine-user
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: focht(a)gmx.net
Created an attachment (id=9265)
--> (http://bugs.winehq.org/attachment.cgi?id=9265)
trace with WINEDEBUG=+tid,+message,+win,+server
Hello,
I've seen this bug a while ago in other apps but ignored it because it was not
easily to reproduce.
Well until recently when I tested some stuff with windbg from "Debugging Tools
for Windows" (Microsoft).
I used debugging tools version 6.8.4.0 and recent GIT
(wine-0.9.49-302-g58b85bb).
Immediately when a child window was opened using toolbar (register, locals, ..
whatever), windbg would become unresponsive, eating most CPU.
Happens in both GUI modes - "floating/docking toolwindow" and "MDI emulation.
Though "MDI emulation" is more obvious, it actually shows the endless
refreshing (window caption).
Attached is WINEDEBUG=+tid,+message,+win,+server log.
Additionally I added a trace message which prints the current queue paint count
(when incremented or fetched) which makes some things easier to spot.
Printed as "inc_queue_paint_count: %d" and "get_message_paint_count: %d".
The window hierarchy is as follows:
--- snip ---
*root*=0x10020
Shell_TrayWnd=0x10022
WinDbgFrameClass=0x10024
DockClass=0x10026
ToolbarWindow32=0x10028
msctls_statusbar32=0x1002a
tooltips_class32=0x1002e
WinBaseClass=0x10030
ToolbarWindow32=0x10032
SysListView32=0x10034
SysHeader32=0x10036
RichEdit20W=0x10038
--- snip ---
After the child windows are created the queue paint count never drops to zero,
resulting in endless WM_PAINT processing.
Maybe some update (region) code path missed or flags problem?
I played a bit with ignoring null region updates and it seemed to help a bit
(preventing endless WM_PAINT loop) though other stuff wasn't drawn properly
then.
Regards
--
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=57845
Bug ID: 57845
Summary: Bug with installing PUBG Mobile on Tencent Gameloop
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: bithit_official(a)mail.ru
Distribution: ---
Created attachment 78063
--> https://bugs.winehq.org/attachment.cgi?id=78063
its a backtrace
I decided to install PUBG MOBILE on my computer via Wine using Tencent
Gameloop. When all the game components had already been downloaded and the
installation itself began, an error appeared from wine: A serious error
occurred in the AndroidEmulatorEn.exe program. I don't know how to fix this and
what is it related to, Wine or Gameloop? Please help 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.