https://bugs.winehq.org/show_bug.cgi?id=46441
Bug ID: 46441
Summary: Steam shows an extra icon when minimizing window
Product: Wine
Version: 4.0-rc5
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
Distribution: ---
Created attachment 63223
--> https://bugs.winehq.org/attachment.cgi?id=63223
screenshot
Steps to reproduce:
1. Enable virtual desktop
2. Launch Steam
3. Minimize window
wine-4.0-rc5-14-g0ff7fd1259
--
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=47331
Bug ID: 47331
Summary: Steam browser flickering
Product: Wine-staging
Version: 4.9
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: werifGX(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
As referenced on https://github.com/PhoenicisOrg/scripts/issues/994 steam
installed using `winetricks 20190310-next` on debian buster using `wine-4.9
(Staging)` which has win7 environment, gameoverlayrenderer dll_override
disabled and CSMT enabled result in flickering of steam browser as presented on
https://youtu.be/LaR8nQ0Ir2w
Suspecting this beeing wine 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=57635
Bug ID: 57635
Summary: Battle.net Launcher invisible/black with the Wayland
driver
Product: Wine
Version: 10.0-rc4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winewayland
Assignee: wine-bugs(a)winehq.org
Reporter: wine(a)xarov.net
Distribution: ArchLinux
Created attachment 77764
--> https://bugs.winehq.org/attachment.cgi?id=77764
Black window with Wayland driver
Works fine with the X11 driver. Is completely black with the Wayland driver.
--
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=56721
Bug ID: 56721
Summary: EA App: multiple assertion failure with Vulkan
renderer
Product: Wine
Version: 9.8
Hardware: x86-64
URL: https://origin-a.akamaihd.net/EA-Desktop-Client-Downlo
ad/installer-releases/EAappInstaller.exe
OS: Linux
Status: NEW
Keywords: download
Severity: minor
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: imwellcushtymelike(a)gmail.com
Distribution: Ubuntu
Created attachment 76502
--> https://bugs.winehq.org/attachment.cgi?id=76502
Wine 9.9 console output
Launching the EA App with renderer=vulkan opens a dialog three times for an
Assertion Failure. Clicking OK three times allows the app to continue, so it's
not clear which of the many sub-/backround processes is causing the issue. No
backtrace is presented.
"winetricks arial" to work around Bug 32342.
renderer=gl does not have 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=54948
Bug ID: 54948
Summary: EA app fails after login
Product: Wine
Version: 8.8
Hardware: x86-64
URL: https://www.ea.com/ea-app
OS: Linux
Status: NEW
Keywords: download
Severity: minor
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
Distribution: ---
d3dcompiler_47 (x64) putted in '../Program Files/Electronic Arts/EA Desktop/EA
Desktop'
After login the app main window shows for a second and then immediately closes.
Disabling d3d12 helps.
0a88:fixme:dxgi:d3d12_swapchain_init Ignoring swap effect 0x4.
0a88:fixme:dxgi:d3d12_swapchain_init Ignoring swapchain flags 0x2.
Assertion failed: !status, file ../wine/dlls/winevulkan/loader_thunks.c, line
160
0324:err:seh:call_stack_handlers invalid frame 000000001C07EA48
(000000001C082000-000000001C180000)
0324:err:seh:call_stack_handlers invalid frame 000000001C07C820
(000000001C082000-000000001C180000)
0324:err:seh:NtRaiseException Exception frame is not in stack limits => unable
to dispatch exception.
8.8-34-gd54e7cd51db
--
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=50155
Bug ID: 50155
Summary: Ableton Live: multicore audio processing causes high
CPU usage across multiple audio backends
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sirwinstoncat5(a)gmail.com
Distribution: Ubuntu
When running Ableton Live, if multicore audio processing is enabled, CPU usage
will drastically increase, causing unpredictable audio crackles and overall
unstable performance.
The easiest way to test this is using Ableton Live 9; Live 10 also has the same
issue, but multicore audio processing is permanently turned on.
- Open an empty Live Set. (By default, this has 4 empty tracks, a reverb
effect, and a delay effect: a negligible amount of audio processing.)
- In Ableton's preferences, under the CPU tab, disable multicore audio
processing. Observe the built-in CPU meter in the upper-right corner; it should
sit very low (0-1% on my system).
- Enable multicore audio processing. Even with an empty Set, observe that the
CPU meter jumps to at least 10-20%. On Windows, idle CPU usage should remain
identical between single and multicore modes.
- Attempt playback of a nontrivial Set; for example, a few tracks of recorded
audio. A Set that plays back fine in single-core mode will exhibit
unpredictable audio crackling and rapid spikes in CPU usage when using
multicore mode.
I have tested this across multiple versions of Ableton (various versions of 9
and 10 both exhibit this issue), multiple audio interfaces from various
manufacturers (Behringer X32, NI Audio Kontrol 1, onboard chipset audio,
PreSonus FireStudio), and even multiple audio backends (winepulse,
wineasio->JACK). The issue seems to be most pronounced when using pulseaudio,
but it is present across all audio backends.
Most importantly, this issue can be duplicated using wineasio and a JACK server
with the dummy backend (aka not connected to any audio interface).
I am unsure where to start collecting logs for this. One guess: perhaps there
is some sort of delay or sleep occuring while a mutex is being held?
This is possibly related to #47458; however, that specifically refers to a test
case for PulseAudio, whereas this bug occurs across backends.
--
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=55076
Bug ID: 55076
Summary: Steam fills terminal output with "ResizeObserver loop
limit exceeded" messages.
Product: Wine
Version: 8.9
Hardware: x86-64
OS: Linux
Status: NEW
Severity: minor
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: o.dierick(a)piezo-forte.be
Distribution: ---
Created attachment 74626
--> https://bugs.winehq.org/attachment.cgi?id=74626
Steam default terminal output wine 8.9
Hello,
This started after a Steam update sometimes ago I don't remember.
> [0617/144308.788:INFO:CONSOLE(1)] "ResizeObserver loop limit exceeded", source: https://steamloopback.host/index.html?IN_CLIENT=true&LOCAL_HOSTNAME=piezo1&… (1)
Searching the quoted string on the web shows that it's related to Chrome [1],
thus Chrome Embedded Framework too (libCEF).
The constant flow of messages fills the HD with several MB after a few hours.
It may be an application bug, but I can't compare to Windows because there is
no output at all when running steam from the Windows command prompt.
Regards.
[1]
https://stackoverflow.com/questions/49384120/resizeobserver-loop-limit-exce…
--
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=57353
Bug ID: 57353
Summary: Steam: the console is spammed with dxgi d3d11 fixmes
Product: Wine
Version: 9.20
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: m1m1k4tz(a)protonmail.com
Distribution: ---
Created attachment 77324
--> https://bugs.winehq.org/attachment.cgi?id=77324
dxgi
My setup is using the new wow64 mode
--
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=57263
Bug ID: 57263
Summary: Steam doesn't load since may update.
Product: Wine
Version: unspecified
Hardware: x86-64
OS: FreeBSD
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: Alexander88207(a)Protonmail.com
Created attachment 77184
--> https://bugs.winehq.org/attachment.cgi?id=77184
Steam-WINED3D.log
Hello,
since the may update of Steam, Steam doesn't load anymore.
The steamwebhelper seems trying to load but an window never gets created.
Default debug logs have been attached, if there are specific debug channels of
interest please tell me.
The web fonts for using CEF browser and friends are installed.
For comparison: The chromium build 129.0.6668.71 (1343869) • Wednesday, 25 Sep
2024 works without issues.
Thank you in advance!
FreeBSD 14.1
Wine 9.17 (Currently latest in ports at this time of writing)
--
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=39022
Bug ID: 39022
Summary: Mouse cursor shows the wrong symbol
Product: Wine
Version: 1.7.44
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sworddragon2(a)aol.com
Distribution: ---
Starting Steam and going to the menu bar -> Steam and moving the mouse cursor
over the entry "Check for Steam Client Updates..." and then stopping the mouse
results that the mouse cursor is showing the I symbol (the cursor symbol that
for example also appears if moving the mouse cursor over a text area). Moving
the mouse shows the normal mouse cursor again but stopping the mouse on the
entry again shows the I symbol again. A workaround seems to be to close the
menu and reopening it.
--
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.