https://bugs.winehq.org/show_bug.cgi?id=51602
Bug ID: 51602
Summary: Roblox Player crash when
server-default_integrity/0007-ntdll-Elevate-processes-
if-requested-in-RtlCreateUse.patch is applied
Product: Wine-staging
Version: 6.9
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: a0939712328(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 70451
--> https://bugs.winehq.org/attachment.cgi?id=70451
The Wine-Staging patch that causes the crash.
A recent update to Roblox Player cause Wine-staging to crash with the error "An
unexpected error occurred and Roblox needs to quit. We're sorry!".
To locate the exact patchset that caused the issue, I created a bisect tool in
Python that allows me to approximately rule out half of the patchsets every
rebuild.
After few rounds of bisection, I discovered that by skipping just the
server-default_integrity patchset, Roblox Player no longer crash.
I did further bisect and found that applying
"0007-ntdll-Elevate-processes-if-requested-in-RtlCreateUse.patch" causes Roblox
Player to crash.
The patch was introduced on commit be3928a8091e36197bc9894c4a09f13cf5459138
(server-default_integrity: Elevate processes if the manifest requests.), which
is supposed to fix Bug ID 51000.
The patch file itself is attached below to make the discussion easier.
--
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=51085
Bug ID: 51085
Summary: Overwatch crashes when launched from Battle.net
Product: Wine-staging
Version: 6.7
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: b1779506(a)trbvn.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Always crashes. wine-6.7 (Staging) on Ubuntu 21.04.
--
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=50558
Bug ID: 50558
Summary: ntdll-Dealloc_Thread_Stack cause memory leak for C#
game
Product: Wine-staging
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: trufanovan(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
I've traced down a memory leak in one game to the ntdll-Dealloc_Thread_Stack in
wine-staging. No other wine versions or staging patches cause such problem.
I've reproduced it on actual wine master branch from github with
`./staging/patchinstall.py ntdll-Dealloc_Thread_Stack`
The game is "Delta's Shadow" released in 2020. Demo is available at
https://zxonline.net/game/deltas-shadow/
Its Windows version is written in C# with SDL.
The memory leaks every time game plays SFX and only in this case. A music
doesn't cause leak. I've asked the author: music is played via SDL and SFX is
played with System.Media.SoundPlayer::Play(). It looks like this class is just
calls PlaySound function from winmm.dll and pass a stream with WAV into it. And
this somehow and ups in ntdll.
So, to reproduce the problem:
1. Install wine-staging
2. Install the demo
3. Launch game in wine-staging
4. Press ALt+Enter to switch the game into a windowed mode and launch Task
manager to see the RAM it consumes.
5. Start pressing W and S keys (Up and Down) in game main menu to produce a
menu item change SFX.
Result:
Game RAM usage grows each time you press the key and don't decrease later.
Expected:
No significant RAM usage change.
--
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=51172
Bug ID: 51172
Summary: Blank screen with many games using wine-staging 6.9
and Arch (wine 6.9 works OK)
Product: Wine-staging
Version: 6.9
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: vulture6(a)mail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ArchLinux
Most games now just give a blank screen when they are run with wine-staging 6.9
on my Arch distro. Can list some if necessary, but should be obvious. No clear
errors from debug log. Changing to standard wine 6.9 fixes problem.
System: Core i5 with Intel UHD 630.
--
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=51198
Bug ID: 51198
Summary: regression: black screen in main menu of warcraft 3
reforged with wine-staging-6.9
Product: Wine-staging
Version: 6.9
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: idarktemplar(a)mail.ru
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 70072
--> https://bugs.winehq.org/attachment.cgi?id=70072
wc3.log.bz2
When running Warcraft 3 Reforged in wine-staging 6.9, main menu is a completely
black screen, and instead of cursor there are some visual artefacts.
With wine-staging 6.8 it works acceptably: it's really slow, but at least
there's properly rendered main menu.
No DXVK is used.
OS: Gentoo Linux, kernel 5.10.27
Proprietary Nvidia driver 460.67:
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GTX 750/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 460.67
OpenGL core profile shading language version string: 4.60 NVIDIA
Wine output contains a lot of lines similar to:
03bc:err:d3d:state_undefined Undefined state UNKNOWN_STATE(0) (0).
Log is 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=50520
Bug ID: 50520
Summary: Any Rust-Lang application: Cannot create an async tcp
connection
Product: Wine
Version: 5.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: winsock
Assignee: wine-bugs(a)winehq.org
Reporter: winehq(a)greaka.de
Distribution: ---
Created attachment 69183
--> https://bugs.winehq.org/attachment.cgi?id=69183
minimal example
Rust applications are not able to use async libraries in wine. TCP connections
send Syn, receive Syn/Ack, send Reset.
Test matrix:
- Wine versions 5.0, 5.8, 5.22, 6.0rc0 , 6.0rc6
- Ubuntu, Arch
- WSL, native on laptop
- Tokio, Smol, Async-Std (Smol and async-std use the same under the hood)
- Rust versions 1.48 stable, 1.49 stable, 1.50 beta
- Targets windows-gnu, windows-msvc
- Toolchains gnu, msvc
Every combination fails to connect.
Minimal example source code: https://pastebin.com/SZavTYD7
precompiled binary 1.50 beta/windows-msvc/msvc attached.
The example expects a listener on localhost:41206!
You can easily open one with ncat -l -k -p 41206
The error returned to rust:
[src\main.rs:10] TcpStream::connect(addr.as_slice()).await = Err(
Os {
code: 10045,
kind: Other,
message: "OS Error 10045 (FormatMessageW() returned error 317)",
},
)
Trace from wineserver:
Short version
https://cdn.discordapp.com/attachments/596410107726921728/79886280364864308…
Long version
https://cdn.discordapp.com/attachments/596410107726921728/79885875841138688…
--
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=51725
Bug ID: 51725
Summary: 7-zip 19.0 (up to 21.03) crashes opening Z: or local
file system
Product: Wine-staging
Version: 6.16
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: noabody(a)yahoo.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 70609
--> https://bugs.winehq.org/attachment.cgi?id=70609
Log of both wine/staging 6.16
See attachment:
System: Manjaro 21.1.2 (Arch-like)
Summary: wine-6.16, 7-zip 19.00 through 21.03 can open "Z:" drive local
filesystem without issue.
wine-6.16 (Staging), 7-zip 19.00 through 21.03 cannot open "Z:" drive
local filesystem without immediate crash.
See 7zip.org to download and test.
--
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=48483
Bug ID: 48483
Summary: Mouse cursor always visible in Gothic 2 with D3D11
renderer
Product: Wine-staging
Version: 5.0-rc4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: supercoolemail(a)seznam.cz
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Gothic 2 (Russian with 2.6 no-cd patch) with D3D11 renderer shows X11/KDE mouse
all the time. Cursor should not be visible in Gothic 2 at all. It does not have
any functional impact but it's disturbing.
How to reproduce:
- Get Gothic 2.
- Test G2 works (menu at least).
- Extract GD3D11 (e.g. from
https://github.com/Kirides/GD3D11/releases/download/v17.7-dev8/Gothic2-GD3D…
but even old versions from Liker suffer from same issue). DLLs from archive
belong to `<game dir>/System` directory.
- Start the game with `ddraw=n,b`.
- See that mouse cursor appears when menu finishes loading. Alternatively,
mouse movements make cursor appear even before menu finishes loading.
There is some analysis here https://github.com/Tk-Glitch/PKGBUILDS/issues/428 .
I can confirm that same issue happens with clean wine-staging 5.0rc4 from Arch
repositories (also with wine-tkg built from master). While clean G2 works
properly in vanilla wine, GD3D11 needs staging otherwise it crashes at startup.
Tested on
`Linux coolhost 5.4.12-arch1-1 #1 SMP PREEMPT Tue, 14 Jan 2020 21:44:31 +0000
x86_64 GNU/Linux`
Ryzen 7 1700
RX 580 8G
16 G RAM
mesa 19.3.2
--
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=48945
Bug ID: 48945
Summary: "Show Advanced Fields" link should be made more
visible and changed to a button
Product: WineHQ Bugzilla
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: bugzilla-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: stefan.riesenberger(a)gmail.com
CC: austinenglish(a)gmail.com
Distribution: ---
Created attachment 66919
--> https://bugs.winehq.org/attachment.cgi?id=66919
Example modification of the "Show Advanced Fields" button
This is a enhancement bug about the bug report page itself.
The "Show Advanced Fields" link isn't really eye catching and blends in with
labels or links that will move you to other pages. I would suggest changing it
to a real button instead, which would make it's function more obvious.
The placement could also be improved, but that's not as important. Currently it
gets overshadowed by the components list, so you pretty much overlook it. I
would suggest moving it between the version and summary field.
I attached a screenshot on how I think it should look like, but as said above
the button position is probably more subjective.
I hope I explained everything in an understandable way.
Kind regards,
Riesi
--
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.