https://bugs.winehq.org/show_bug.cgi?id=43702
Bug ID: 43702
Summary: No comments shown if no maintainers for app
Product: WineHQ Apps Database
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: appdb-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: azrdev(a)qrdn.de
Distribution: ---
If an app has no maintainers, it shows "comments disabled", and one cannot
enter new comments. This is useful, because no one would moderate them.
However, it would still be useful to see the backlog of old comments, which may
contain hints and workarounds posted by users (when there still were
maintainers).
--
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=54300
Bug ID: 54300
Summary: LdrLoadDll illegal memory access on DllPath
Product: Wine
Version: 7.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: novae.harpist06(a)icloud.com
Distribution: ---
Created attachment 73867
--> https://bugs.winehq.org/attachment.cgi?id=73867
Reproducer
See reproducer (attached)
DllPath can be search flags, which is indicated by passing a pointer where the
lowest bit is set. This is not handled in wine, which calls wcslen on it:
https://github.com/wine-mirror/wine/blob/a8c1d5c108fc57e4d78e9db126f395c890…
The path resolution is correctly implemented in LdrGetDllPath, but that
function is not used (besides being an export).
Windows output:
Trying flag 00000200
Trying flag 00000400
Trying flag 00000800
Trying flag 00001000
Trying flag 00002000
Trying flag 00004000
Wine output:
Trying flag 00000200
wine: Unhandled page fault on read access to 0000000000000201 at address
0000000170069B40 (thread 05ec), starting debugger...
--
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=55915
Bug ID: 55915
Summary: Shader Compiler Issues
Product: Wine
Version: 8.20
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: d3d
Assignee: wine-bugs(a)winehq.org
Reporter: wschmrdr(a)gmail.com
Distribution: ---
Created attachment 75465
--> https://bugs.winehq.org/attachment.cgi?id=75465
Shader Compiler Errors Found
When attempting to play StarCraft II using a custom map (StarCraft Mass Recall
latest version to be precise), I noticed the attached in the log when starting.
Nothing on either side of this trace seemed out of the ordinary.
As a side note (don't know if it's related but I'll note it anyway), Map 5 of
Loomings ("Extermination") does seem to have the same graphics crash previously
reported when I build a Machine Shop off the Factory or try to attack the first
base.
--
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=43849
Bug ID: 43849
Summary: Heroes of the Storm; crashes when Call Mech effect is
on-screen
Product: Wine
Version: 2.18
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jonathan(a)pearce.name
Distribution: ---
Steps to reproduce:
Start Heroes of the Storm.
Enter Try mode with D.Va.
Take tower damage until your mech is dead.
Shoot enemies until your Call Mech cooldown is activated.
Use Call Mech 'E'.
The mech arrival effect will begin but the game will crash before the mech
becomes visible on-screen. A dialog box pops up with a
e_gfxerrorshadercompilefailed error.
Relevant wine stdout:
fixme:d3dx:D3DXLoadSurfaceFromMemory Unhandled filter 0x80004.
fixme:d3dx:D3DXLoadSurfaceFromMemory Unhandled filter 0x80004.
fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
fixme:msvcp:_Mtx_init_in_situ unknown flags ignored: 2
fixme:hlsl_parser:hlsl_parse Check for valued return on void function.
fixme:hlsl_parser:hlsl_parse Implicit conversion to the return type if needed,
error out if conversion not possible.
err:d3dcompiler:compile_shader HLSL shader parsing failed.
fixme:dbghelp:elf_search_auxv can't find symbol in module
fixme:d3dx:D3DXLoadSurfaceFromMemory Unhandled filter 0x80004.
fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub
I experimented with
winetricks d3dx9_43
but that didn't fix the crash (it does change the error signature).
I also tried
d3dcompiler_43 (native)
but it didn't seem to matter.
--
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=43775
Bug ID: 43775
Summary: Heroes of the Storm crash on start with d3d11
Product: Wine
Version: 2.17
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: maxi.cass11(a)gmail.com
Distribution: ---
Created attachment 59282
--> https://bugs.winehq.org/attachment.cgi?id=59282
terminal Output 2.17-staging with dx11
I don't know if the bug is in the non-staging version because Battlenet crash
in non-staging.
My game crash on my laptop with d3d11, I need to set the -dx9 argument to
correct this.
--
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=55986
Bug ID: 55986
Summary: Gunner3 has flickering in fullscreen
Product: Wine
Version: 8.21
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: ---
Since wine-6.1 there is flickering when running Gunner3 in fullscreen mode.
Also, from time to time old frame data is shown for a few moments making the
game
It works with winecfg virtual desktop mode, and making screenshots in
fullscreen is hard. It looks similar to the glitches in bug 45168 (but it is
unrelated).
Don't try to click on a level without having the fix from bug 41977 though, it
might crash. The menu is enough to reproduce the 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=52244
Bug ID: 52244
Summary: starcraft2 crashes while loading arcade game
e_gfxErrorShaderCompileFailed
Product: Wine
Version: 6.23
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: cedric.dewijs(a)eclipso.eu
Distribution: ---
Created attachment 71352
--> https://bugs.winehq.org/attachment.cgi?id=71352
console messages
[cedric@cedric ~]$ wine --version
wine-6.23
[cedric@cedric ~]$ uname -a
Linux cedric 5.15.8-arch1-1 #1 SMP PREEMPT Tue, 14 Dec 2021 12:28:02 +0000
x86_64 GNU/Linux
[cedric@cedric ~]$ rm -rf ~/.wine
[cedric@cedric ~]$ wineboot
[cedric@cedric ~]$ wine ~/.wine-sc2-ok/drive_c/Program\ Files\
\(x86\)/StarCraft\ II/StarCraft\ II.exe
Install battle.net (it finds starcraft2), close
click Play
choose custom -> arcade. Type in "coop" into the search field, and click on
"Wings of liberty coop 1. Liberation day", and click create lobby, and then
click "start game".
After the countdown, the loading screen shows up, and the progress bar goes
about to half full. Then this error dialog shows up:
"Starcraft II
e_gfxErrorShaderCompileFailed
To help us identify the problem, please describe what you were doing when the
error occurred.
Please use the Report ID below when communicating with Blizzard about the
issue.
DF97FB56-8356-44A6-A960-5BEA033C44DA
[X] Send to Blizzard [Reopen] [Close]"
--
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=23015
Summary: PL\SQL Developer: shows standard message boxes behind
main window
Product: Wine
Version: 1.2-rc2
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: comdlg32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: chaostya(a)gmail.com
When I write a query in PL\SQL Developer window, then issue it against DB and
then want to close the window I click [x] and it looks like nothing happens,
but if I move main window down I would see a standard "question" message dialog
box asking me if I want to save my changes. I'm on 1.2-rc2 and it's a
regression from 1.2-rc1
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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=45039
Bug ID: 45039
Summary: Mono: System.UnauthorizedAccessException when trying
to read from stdin when both stdout and stderr are
redirected
Product: Wine
Version: 3.6
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mk+winehq1803(a)pimpmybyte.de
Distribution: ---
I wrote a simple C# program that reads a line from stdin and prints it in
uppercase (01_shout.cs in [1]).
The exe (compiled on Ubuntu with "mcs") is available for download at
http://l.proggr.de/?1839m7ier
It accepts interactive input when run in cmd.exe on windows 7, even with both
stdout and stderr redirected (02_log_win7.txt in [1]).
In Ubuntu, it crashes when trying to read the line while stdin is a TTY and
both stdout and stderr are redirected (03_log_wine.txt in [1]).
Ubuntu 14.04.5 LTS trusty, wine-3.6,
Mono JIT compiler version 3.2.8 (Debian 3.2.8+dfsg-4ubuntu1.1)
Kernel 3.13.0-142-generic #191-Ubuntu SMP Fri Feb 2 12:14:37 UTC 2018 i686 i686
i686 GNU/Linux
[1] https://gist.github.com/mk-pmb/adae211e875ff11274d9b81248d033a3
--
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=44840
Bug ID: 44840
Summary: Icewind Dale unusably glitchy starting with Wine
Version 3.2
Product: Wine
Version: 3.4
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: wodencafe(a)gmail.com
Distribution: ---
Starting with Wine 3.2 and on, Icewind Dale (2.0.0.11 (GOG)) is having very
strange input / glitchy rendering issues.
I have attached a video comparison with 3.1 where it works fine.
Tested with 3.2, 3.3, and 3.4, and all have the strange input and glitchy
problem.
There are no additional wine modifications.
Please see the video for example of problem, and comparison of when it was
working with 3.1
--
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.