https://bugs.winehq.org/show_bug.cgi?id=50665
Bug ID: 50665
Summary: Inconsistent behavior of kernel32.OutputDebugStringA/W
API with regards to Wine 'debugstr' and 'seh' debug
channel usage
Product: Wine
Version: 6.2
Hardware: x86-64
OS: Linux
Status: NEW
Severity: enhancement
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: focht(a)gmx.net
Distribution: ---
Hello folks,
before commit
https://source.winehq.org/git/wine.git/commitdiff/3b002685fe18ca3985af744d8…
("kernel32: Move debugger functions to kernelbase.") one could use 'debugstr'
channel facility for apps/drivers that make use of 'OutputDebugStringA/W' API
without all the other debug channels noise. Definitely helpful besides running
the app under a debugger or Sysinternal's 'DebugView' tool.
After that commit one had to use 'seh' debug channel and filter all the
unwanted messages to get a similar result.
With the fix for bug 48059 ("IMVU Social Network Client v539 hangs"), commit
https://source.winehq.org/git/wine.git/commitdiff/4ac3cbd6ccba52ad8d528ee74…
("kernel32: Duplicate OutputDebugStringA implementation.") to old 'debugstr'
debug channel got reintroduced again which leads to inconsistent behavior.
If the app calls 'OutputDebugStringA' - which only few do - one can still use
the old 'debugstr' channel but any 'OutputDebugStringW' calls won't be seen.
That's not very useful.
Either put 'OutputDebugStringA' into 'seh' debug channel or duplicate
'OutputDebugStringW' to kernel32.
$ wine --version
wine-6.2
Regards
--
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=48059
Bug ID: 48059
Summary: IMVU Social Network Client hangs
Product: Wine
Version: 4.19
Hardware: x86
URL: https://secure.imvu.com
OS: Linux
Status: NEW
Keywords: regression
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: z.figura12(a)gmail.com
Regression SHA1: 3b002685fe18ca3985af744d8f147f29b2c588f0
Distribution: ---
There's clearly some nonsense going on with hooking. The game tries to call
kernel32.OutputDebugString(), which, instead of then executing Wine's
implementation, instead goes on to write the message to a file in the game's
directory, repeatedly, in a loop.
Reverting 3b002685f fixes this. Changing kernel32's spec file to forward to
kernelbase instead of using an import thunk also fixes this. What's confusing
me is I can't figure out how the hooking is actually done. Tracing the code of
OutputDebugString(), both A and W versions, both from kernel32 and kernelbase,
never seems to show signs of hooking, i.e. it's entirely identical to the
version on disk.
Note that the application requires an email-based account to be created.
--
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=7054
--- Comment #23 from joaopa <jeremielapuree(a)yahoo.fr> ---
Bug still occurs with wine-6.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=49026
Bug ID: 49026
Summary: Topaz Video Enhance AI: video card support is not
detected.
Product: Wine
Version: 5.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: depositmail(a)mail.ru
Distribution: ---
Topaz Video Enhance AI: video card support is not detected.
--
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=44402
Bug ID: 44402
Summary: Shamela3.64 crashes when opening a book in (non-root)
user mode
Product: Wine
Version: 3.0-rc6
Hardware: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: batou.dum(a)free.fr
Distribution: ---
Created attachment 60329
--> https://bugs.winehq.org/attachment.cgi?id=60329
The backtrace followed by a copy of the end of the terminal output
Shamela is an electronic arabic library which downloads packages, imports the
books which are in it and enable the user to read it and make plain-text
searches.
I use it with Linux 4.9.0-5-amd64 under Debian 6.3.0-18.
When I launch it with Wine as a non-root user, it downloads and imports the
books, but if I select a book to read it crashes. I attached the backtrace with
the end of the terminal output. Sometimes it doesn't do anything when I select
the book, but if I try again it crashes.
(It does run well with Wine when I execute it as root, yet it doesn't seems to
me a good idea to do it.)
If you want to install the program, you can download it at :
http://d.shamela.ws/downloads/shamela3.64.rar
Then simply uncompress it and run wine ~/shamela3.64/_shamela.exe.
(If you want a correct arabic display, you can use this tutorial :
https://abuhirr.wordpress.com/2013/12/20/syamilah/. GoogleTranslate from
Indonesian to English works quite fine ! But I don't think it necessary if you
don't read Arabic.)
Look here for the meaning of the icons :
http://uloom.com/edu/mod/page/view.php?id=151.
Normally, when opening the program will open a small window. Click on the right
button. If it doesn't, click on the "upgrade" button (first on the left in the
most recent versions).
Then unselect all the directories (it will take a few seconds if you do it by
unselecting the parent directory), open the first directory, select the first
book and press the right button in the bottom-right corner. When the next
question appears, click on the left button.
When the download ends, wait a little and click on the "Select book" icon
(first on the right). Open the first directory and double-click on the book. If
you are not in root, a window should appear informing you about the error.
Click on the right button in the bottom-left corner to see the backtrace, and
again on the right button to save 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.
https://bugs.winehq.org/show_bug.cgi?id=50284
Bug ID: 50284
Summary: FSCTL_GET_REPARSE_POINT doesn't contain any target for
a symbolic link
Product: Wine-staging
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: martin(a)martin.st
CC: erich.e.hoover(a)gmail.com, leslie_alistair(a)hotmail.com,
z.figura12(a)gmail.com
Distribution: ---
Created attachment 68841
--> https://bugs.winehq.org/attachment.cgi?id=68841
Test program
https://github.com/wine-staging/wine-staging/blob/fce121fcd95380ca56c9d027b…
does contain some support for reading relative symlinks, but it doesn't seem to
work currently; the SubstituteNameLength and PrintNameLength fields of
SymbolicLinkReparseBuffer are zero after a call to
DeviceIoControl(FSCTL_GET_REPARSE_POINT), see the attached test program.
--
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=50303
Bug ID: 50303
Summary: MSI package installation fails in wine-staging
Product: Wine-staging
Version: 6.0-rc1
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: regression
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: gyebro69(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 68874
--> https://bugs.winehq.org/attachment.cgi?id=68874
terminal output during prefix creation (Wine-Mono fails to install)
This may be related to bug #50036.
The problem is present in Staging since
https://github.com/wine-staging/wine-staging/commit/f9e86098b3136869479621e…
For example when you create a new prefix, the Wine-Mono package fails to
install.
The same failure occurs when I try to install Nvidia Physx via winetricks.
Works properly with the previous staging commit:
https://github.com/wine-staging/wine-staging/commit/023588ac34c3314d18f4ebb…
--
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=50036
Bug ID: 50036
Summary: Remaining issues in Bugs in ntdll-Junction_Points in
staging
Product: Wine-staging
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: martin(a)martin.st
CC: erich.e.hoover(a)gmail.com, leslie_alistair(a)hotmail.com,
z.figura12(a)gmail.com
Distribution: ---
Created attachment 68477
--> https://bugs.winehq.org/attachment.cgi?id=68477
Test code for showing the issue
With the ntdll-Junction_Points, there's a few remaining issues that are
unimplemented:
- When opening a symbolic link with CreateFile(), it doesn't take the
FILE_FLAG_OPEN_REPARSE_POINT flag into account. E.g. if the symlink points at a
nonexistent file, if the link is opened with CreateFile() with the
FILE_FLAG_OPEN_REPARSE_POINT flag set, the operation should succeed (inspecting
the link), but without the flag, it should fail (as the link points at a
nonexistent file). Currently, it succeeds in both cases.
- If inspecting the handle opened with CreateFile() with
GetFileInformationByHandleEx(FileAttributeTagInfo), the ReparseTag field is
left zero.
This can be tested with the attached test app. On real windows, it prints
something like this:
CreateFile(FILE_FLAG_OPEN_REPARSE_POINT) = 0000000000000094
ReparseTag = a000000c
CreateFile(0) = FFFFFFFFFFFFFFFF
While on wine with the ntdll-Junction_Points patchset applied, it prints:
CreateFile(FILE_FLAG_OPEN_REPARSE_POINT) = 000000000000003C
ReparseTag = 0
CreateFile(0) = 000000000000003C
ReparseTag = 0
--
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=50283
Bug ID: 50283
Summary: FILE_OPEN_REPARSE_POINT breaks error reporting for
deletes of directories
Product: Wine-staging
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: martin(a)martin.st
CC: erich.e.hoover(a)gmail.com, leslie_alistair(a)hotmail.com,
z.figura12(a)gmail.com
Distribution: ---
Created attachment 68840
--> https://bugs.winehq.org/attachment.cgi?id=68840
Test program
In order to generically delete a file system entry, regardless of whether it is
a regular file, symlink or directory, one can open a handle to it and delete it
with a call to SetFileInformationByHandle(FileDispositionInfo). By opening the
handle with FILE_FLAG_OPEN_REPARSE_POINT, a potential symlink gets handled by
removing the symlink itself, not the target file it points to.
If a handle opened with the FILE_FLAG_OPEN_REPARSE_POINT flag set turns out to
be a directory, error reporting for the SetFileInformationByHandle call fails.
This is caused by [1] in combination with [2]. These two cases make O_SYMLINK,
which includes O_PATH, be added when opening the file descriptor which turns
out to be a directory. The O_PATH flag causes the later fdopendir() and
readdir() to not return anything, causing is_dir_empty [3] to indicate that the
directory is empty and removal will succeed, even though it doesn't.
This triggers errors in a std::filesystem testcase in libc++ [4], when checking
to make sure that attempts to remove a non-empty directory properly signals
errors.
[1]
https://github.com/wine-staging/wine-staging/blob/fce121fcd95380ca56c9d027b…
[2]
https://github.com/wine-staging/wine-staging/blob/fce121fcd95380ca56c9d027b…
[3]
https://source.winehq.org/git/wine.git/blob/fac1e40aaf0726a3e328a922cb49692…
[4]
https://github.com/llvm/llvm-project/blob/1e260f955d3123351fc68de8c2dde02b1…
The issue can be reproduced with the attached fairly minimal test program.
--
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=49782
Bug ID: 49782
Summary: Elite Dangerous Horizons: crashes with wine64 5.16
Product: Wine
Version: 5.16
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: klaus.heissler(a)tutanota.com
Distribution: ---
Created attachment 68098
--> https://bugs.winehq.org/attachment.cgi?id=68098
terminal output
The launcher and game starts normally and gets all the way to the main menu
where it tries to connect to game servers for ~10 seconds and crashes after
that.
Works normally when downgraded to wine64 5.15.
Regression Testing: (This was done in the existing prefix as I had problems
installing dotnet40 to a new one)
75e616d52b452d37cc93f492d47eba641f9741c1 is the first bad commit
commit 75e616d52b452d37cc93f492d47eba641f9741c1
Author: Alexandre Julliard <julliard(a)winehq.org>
Date: Thu Aug 27 11:41:36 2020 +0200
ntdll: Clear the syscall frame on return instead of popping the previous
one.
Signed-off-by: Alexandre Julliard <julliard(a)winehq.org>
dlls/ntdll/unix/signal_arm.c | 23 +++++++-------
dlls/ntdll/unix/signal_arm64.c | 38 ++++++++++-------------
dlls/ntdll/unix/signal_i386.c | 48 +++++++++++++----------------
dlls/ntdll/unix/signal_x86_64.c | 63 +++++++++++++++++---------------------
tools/winebuild/import.c | 67 ++++++++++++++++++-----------------------
5 files changed, 105 insertions(+), 134 deletions(-)
Operating System: Arch Linux
KDE Plasma Version: 5.19.5
KDE Frameworks Version: 5.73.0
Qt Version: 5.15.0
Kernel Version: 5.8.5-arch1-1
OS Type: 64-bit
Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor
Memory: 31,4 GiB of RAM
Graphics Processor: GeForce GTX 1070/PCIe/SSE2 // Nvidia proprietary 450.66-16
--
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=50141
Bug ID: 50141
Summary: PASCO Capstone: installed and worked until OS update
(and wine update with it) and now shows error on boot
Product: Wine
Version: 5.20
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: winkelnp04(a)gmail.com
Distribution: ---
Created attachment 68639
--> https://bugs.winehq.org/attachment.cgi?id=68639
Error File
On Manjaro. PASCO Capstone (software required in my Physics course) installed
and worked fine until November Manjaro update, with updated wine packages. Now
it installed fine, but doesn't start. I tried installing it with older versions
of wine, but 1.13+ give the same error now, and anything below starts the
program, but shows no content (as if it couldnt load part of the code, since
the menubar shows up)
I know this seems like a Manjaro problem, but could it maybe also be a wine
problem?
sorry if i'm doing this wrong.
--
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=50081
Bug ID: 50081
Summary: Kate on Windows needs
msvcp140_1.dll._Aligned_get_default_resource
Product: Wine
Version: 5.20
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: msvcp
Assignee: wine-bugs(a)winehq.org
Reporter: mywine(a)schiermeier-it.de
Distribution: ---
Created attachment 68536
--> https://bugs.winehq.org/attachment.cgi?id=68536
Logging in (KDE-) Konsole during start
The windows version of the editor Kate crashes during startup. Looks like
#49954.
--
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=49483
Bug ID: 49483
Summary: snapcamera crashes at start
Product: Wine
Version: 5.11
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: animegirl(a)stronzi.org
Distribution: ---
Created attachment 67597
--> https://bugs.winehq.org/attachment.cgi?id=67597
crash log
kUbuntu 20.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=42707
Bug ID: 42707
Summary: World of Warships: Cannot display inventory and clan
screens
Product: Wine
Version: 2.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: Andreas.Schallenberg(a)Eurobild.com
Distribution: ---
Created attachment 57682
--> https://bugs.winehq.org/attachment.cgi?id=57682
Backtrace when opening clan screen
WoWS cannot enter Inventory screen or clan screen. When trying, it opens up a
semi-transparent layer with a anchor-symbol with an animation. This step
happens on Windows as well to indicate the loading. Under wine there is no
further progress. In the better case, the screen stays as is forever. In the
worse case (happens most often with inventory) there is a stack backtrace being
displayed. In both cases the user can proceed by closing the semi-transparent
layer.
Environment:
- World of Warships v0.6.2.2 (issue is the same with older versions)
- Wine 2.4 (downloaded from
http://download.opensuse.org/repositories/Emulators:/Wine/openSUSE_Leap_42.…)
- Linux jordan 4.4.49-16-default #1 SMP Sun Feb 19 17:40:35 UTC 2017 (70e9954)
x86_64 x86_64 x86_64 GNU/Linux
--
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=39472
Bug ID: 39472
Summary: World of Warships 0.4.x/0.5.x client runs out of GL
memory after many consecutive games
Product: Wine
Version: 1.7.53
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: focht(a)gmx.net
Distribution: ---
Hello folks,
by having a large number of consecutive games within same session, the client
will eventually run out of GL memory.
Not sure if this is a Wine bug or a bug in the game engine itself.
It doesn't matter if ARB or GLSL shader backend (default), CSMT or non-CSMT
(default) is used.
Plain Wine and Wine-Staging (for CSMT).
The leak is around 50-70 MB per game so it takes 20-30 games until it becomes
apparent.
When that happens you get strange effects due to failing GL calls.
Console output at the exact point:
--- snip ---
...
0028:err:d3d_texture:texture2d_prepare_texture >>>>>>>>>>>>>>>>>
GL_OUT_OF_MEMORY (0x505) from glTexImage2D @
/home/focht/projects/wine/wine.repo/staging-src/dlls/wined3d-csmt/../wined3d/texture.c
/ 1000
0028:err:d3d_texture:wined3d_texture_bind >>>>>>>>>>>>>>>>> GL_OUT_OF_MEMORY
(0x505) from glGenTextures @
/home/focht/projects/wine/wine.repo/staging-src/dlls/wined3d-csmt/../wined3d/texture.c
/ 199
0028:err:d3d_texture:texture2d_prepare_texture >>>>>>>>>>>>>>>>>
GL_OUT_OF_MEMORY (0x505) from glTexImage2D @
/home/focht/projects/wine/wine.repo/staging-src/dlls/wined3d-csmt/../wined3d/texture.c
/ 1000
0028:err:d3d_surface:wined3d_surface_upload_data >>>>>>>>>>>>>>>>>
GL_INVALID_VALUE (0x501) from glTexSubImage2D @
/home/focht/projects/wine/wine.repo/staging-src/dlls/wined3d-csmt/../wined3d/surface.c
/ 1732
0028:err:d3d_draw:draw_strided_fast >>>>>>>>>>>>>>>>>
GL_INVALID_FRAMEBUFFER_OPERATION (0x506) from glDrawArrays @
/home/focht/projects/wine/wine.repo/staging-src/dlls/wined3d-csmt/../wined3d/drawprim.c
/ 91
005a:trace:seh:__regs_MSVCRT__setjmp3 buf=0x2cc5da20 ebx=351af2d0 esi=2f6c5150
edi=351af2a0 ebp=0ea7e928 esp=0ea7e914 eip=00d65da3 frame=0ea7ea48
0028:err:d3d_surface:surface_blt_fbo >>>>>>>>>>>>>>>>>
GL_INVALID_FRAMEBUFFER_OPERATION (0x506) from glReadBuffer() @
/home/focht/projects/wine/wine.repo/staging-src/dlls/wined3d-csmt/../wined3d/surface.c
/ 1078
0028:err:d3d_draw:draw_strided_fast >>>>>>>>>>>>>>>>>
GL_INVALID_FRAMEBUFFER_OPERATION (0x506) from glDrawArrays @
/home/focht/projects/wine/wine.repo/staging-src/dlls/wined3d-csmt/../wined3d/drawprim.c
/ 91
0028:err:d3d_texture:texture2d_prepare_texture >>>>>>>>>>>>>>>>>
GL_OUT_OF_MEMORY (0x505) from glTexImage2D @
/home/focht/projects/wine/wine.repo/staging-src/dlls/wined3d-csmt/../wined3d/texture.c
/ 1000
0028:err:d3d_shader:shader_arb_select >>>>>>>>>>>>>>>>>
GL_INVALID_FRAMEBUFFER_OPERATION (0x506) from
glBindProgramARB(GL_FRAGMENT_PROGRAM_ARB, priv->current_fprogram_id); @
/home/focht/projects/wine/wine.repo/staging-src/dlls/wined3d-csmt/../wined3d/arb_program_shader.c
/ 4692
0028:err:d3d_draw:draw_strided_fast >>>>>>>>>>>>>>>>>
GL_INVALID_FRAMEBUFFER_OPERATION (0x506) from glDrawArrays @
/home/focht/projects/wine/wine.repo/staging-src/dlls/wined3d-csmt/../wined3d/drawprim.c
/ 91
--- snip ---
I continuously monitor the GPU memory usage using 'nvidia−smi' tool from
another terminal:
--- snip ---
$ watch -n2 nvidia-smi
...
Fri Oct 16 18:26:51 2015
+------------------------------------------------------+
| NVIDIA-SMI 352.41 Driver Version: 352.41 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
|===============================+======================+======================|
| 0 GeForce GTX 850M Off | 0000:01:00.0 Off | N/A |
| N/A 50C P8 N/A / N/A | 1385MiB / 2047MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes: GPU Memory |
| GPU PID Type Process name Usage |
|=============================================================================|
| 0 4151 G /usr/libexec/Xorg 49MiB |
| 0 4485 G ...mes\World_of_Warships\worldofwarships.exe 1325MiB |
+-----------------------------------------------------------------------------+
--- snip ---
Regards
--
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=41314
Bug ID: 41314
Summary: World of Warships (0.5.11) crashes with Critical Error
Occurred
Product: Wine
Version: 1.9.18
Hardware: x86-64
URL: http://worldofwarships.eu/en/game/download/
OS: Linux
Status: NEW
Keywords: download
Severity: minor
Priority: P2
Component: directx-d3dx9
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
Distribution: ---
Created attachment 55645
--> https://bugs.winehq.org/attachment.cgi?id=55645
log
Crashes after login with builtin d3dx9_43 dll.
With native dll works fine.
wine-1.9.18-75-g4bfefc5
--
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=47479
Bug ID: 47479
Summary: REGRESSION: Darkula by Locomalito gives white screen
with Wine 4.12.1
Product: Wine
Version: 4.12.1
Hardware: x86
URL: https://www.locomalito.com/darkula.php
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: vulture6(a)mail.com
Distribution: Mint
As per title, Darkula no longer runs with 4.12.1. Just get a white screen.
Works fine with 4.0.1 and 4.11. Can't see any obvious changes between output.
Sorry, can't run regression test. This is with AMD.
--
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=43774
Bug ID: 43774
Summary: Chromium-based browser engine (CEFv3) used by several
games crashes on shutdown (World of Warships 0.6.x)
Product: Wine
Version: 2.17
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: ntdll
Assignee: wine-bugs(a)winehq.org
Reporter: focht(a)gmx.net
Distribution: ---
Hello folks
to track https://source.winehq.org/patches/data/137313
--- quote ---
ntdll: Do not queue a completion status if pipe ops fail synchronously.
This fixes random crashes when exiting Chromium or shutting down CEF.
It is similar to 7a1142035d7ee04839417176ff93fd0953e2a4e1, just for pipes.
--- quote ---
Can be reproduced with games that use Chromium/CEFv3 as in-game browser, for
example World of Warships 0.6.x.
In World of Warships 0.6.x switch multiple times between "[Port]" and "[CLAN]"
tabs (CLAN page uses in-game browser) to force a crash.
With the patch applied the crash disappears.
NOTE: Currently Wine-Staging must be used for reproduce because there are still
some patches missing from vanilla Wine
(https://github.com/wine-compholio/wine-staging/tree/master/patches/kernel32…
etc.)
--- snip ---
0x11fc9c62: int $3
Modules:
Module Address Debug info Name (186 modules)
PE 400000- 514000 Deferred cef_browser_process
PE 1c20000- 1c94000 Deferred chrome_elf
PE 10000000-14113000 Export libcef
ELF 7a800000-7a942000 Deferred opengl32<elf>
\-PE 7a840000-7a942000 \ opengl32
ELF 7b400000-7b7f5000 Deferred kernel32<elf>
\-PE 7b420000-7b7f5000 \ kernel32
ELF 7bc00000-7bd15000 Dwarf ntdll<elf>
\-PE 7bc30000-7bd15000 \ ntdll
ELF 7c000000-7c004000 Deferred <wine-loader>
...
0000015f (D) C:\Games\World_of_Warships\cef\cef_browser_process.exe
[C:/Games/World_of_Warships/cef/cef_browser_process.exe
--user-agent="Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML,
like Gecko) Chrome/39.0.2171.95 Safari/537.36 WOWS/1.0"
--cache-path="C:/Games/World_of_Warships/profile/cef_cache" --disable-gpu
--disable-gpu-compositing --enable-begin-frame-scheduling --max-frame-rate=30
--log-severity="info" --accept-language-list="en" --id=138]
000001cb 0
...
00000172 0 <==
...
--- snip ---
Disassembly:
--- snip ---
...
11FC9C0D 50 PUSH EAX
11FC9C0E 6A 60 PUSH 60
; ASCII "y:\work\cef3_git\chromium\src\mojo\edk\system\channel_win.cc"
11FC9C10 68 E86E6913 PUSH libcef.13696EE8
11FC9C15 68 286F6913 PUSH libcef.13696F28 ; ASCII "ShutDownImpl"
11FC9C1A 8D4D E0 LEA ECX,DWORD PTR SS:[EBP-20]
11FC9C1D E8 1E1576FE CALL libcef.1072B140
11FC9C22 50 PUSH EAX
11FC9C23 8BCE MOV ECX,ESI
11FC9C25 E8 668176FE CALL libcef.10731D90
11FC9C2A 8D4D FC LEA ECX,DWORD PTR SS:[EBP-4]
11FC9C2D E8 CE290DFE CALL libcef.1009C600
11FC9C32 5E POP ESI
11FC9C33 8BE5 MOV ESP,EBP
11FC9C35 5D POP EBP
11FC9C36 C3 RETN
11FC9C37 55 PUSH EBP
11FC9C38 8BEC MOV EBP,ESP
11FC9C3A 83EC 0C SUB ESP,0C
11FC9C3D 53 PUSH EBX
11FC9C3E 8BD9 MOV EBX,ECX
11FC9C40 8BD3 MOV EDX,EBX
11FC9C42 F7DA NEG EDX
11FC9C44 56 PUSH ESI
11FC9C45 8D43 10 LEA EAX,DWORD PTR DS:[EBX+10]
11FC9C48 1BD2 SBB EDX,EDX
11FC9C4A 23D0 AND EDX,EAX
11FC9C4C 57 PUSH EDI
11FC9C4D 52 PUSH EDX
11FC9C4E E8 1D7A79FE CALL libcef.10761670
11FC9C53 8BC8 MOV ECX,EAX
11FC9C55 E8 367B79FE CALL libcef.10761790
11FC9C5A 8D7B 1C LEA EDI,DWORD PTR DS:[EBX+1C]
11FC9C5D 833F FF CMP DWORD PTR DS:[EDI],-1
11FC9C60 75 01 JNZ SHORT libcef.11FC9C63
11FC9C62 CC INT3 ; triggers CHECK(handle_.is_valid());
11FC9C63 FF37 PUSH DWORD PTR DS:[EDI]
11FC9C65 FF15 E8043513 CALL DWORD PTR DS:[<&KERNEL32.CancelIo>]
11FC9C6B 80BB 85000000 00 CMP BYTE PTR DS:[EBX+85],0
11FC9C72 74 0B JE SHORT libcef.11FC9C7F
...
--- snip ---
https://chromium.googlesource.com/chromium/src/+/refs/heads/master/mojo/edk…
--- snip ---
void ShutDownOnIOThread() {
base::MessageLoop::current()->RemoveDestructionObserver(this);
// BUG(crbug.com/583525): This function is expected to be called once, and
// |handle_| should be valid at this point.
CHECK(handle_.is_valid());
CancelIo(handle_.get().handle);
if (leak_handle_)
ignore_result(handle_.release());
handle_.reset();
// May destroy the |this| if it was the last reference.
self_ = nullptr;
}
--- snip ---
Regards
--
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=43164
Bug ID: 43164
Summary: World of Warships latest update (0.6.6) results in a
critical error on Startup
Product: Wine
Version: 2.10
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: maiktapwagner(a)aol.com
Distribution: ---
Created attachment 58419
--> https://bugs.winehq.org/attachment.cgi?id=58419
World Of Warships Error Message
Hello everyone,
this might be related to 41314 and 38233 but I am having trouble of getting the
latest version of "World of Warships 0.6.6" to run. I am attaching a screenshot
of the error message as well as console output.
Installation was done in a fresh prefix with the European installer
$ sha256sum WoWS_internet_install_eu.exe
c59d3ca1b535c6315a71ef2eda045ccc2f8b207183ef4638f66b45c72d66430e
WoWS_internet_install_eu.exe
Report for the AppDB for this latest version has also been written.
Can you take a look into this please?
--
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=38233
Bug ID: 38233
Summary: world of warships
Product: Wine
Version: 1.7.38
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: kylewatters1(a)hotmail.com
Distribution: ---
Created attachment 51038
--> https://bugs.winehq.org/attachment.cgi?id=51038
world of warships
tried to use this wine to run the game world of warships and it failed. was the
only version that would let me even get the download to work and install etc.
but when i hit play after all updates etc it crashed.
--
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=39602
Bug ID: 39602
Summary: World of Warships: game launched thow unhandled
exception
Product: Wine
Version: 1.7.53
Hardware: x86
OS: FreeBSD
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mazhe(a)alkumuna.eu
Created attachment 52768
--> https://bugs.winehq.org/attachment.cgi?id=52768
Console output
Hi,
I am trying to run the game World of Warships on FreeBSD 10.2 with 32bit wine
version 1.7.53 (not staging).
I followed procedure described on forums to install directx9, wininet and other
dependencies, a procedure that worked on a GNU/Linux (devuan) and a OSX
installations.
On this FreeBSD however, while the initial installer works, the launched that
will then download real game assets and such simply fails with a dialog box
saying:
An unhandled exception is occured. The application will be restarted
With the choice "OK" looping forever with that issue, and "Cancel" exiting. One
more information is that there have been report about trying to enable/disable
torrent download by edition a plain text config file inside the game, but it
did not change anything.
Here is the console output of wine, if somebody could take a look... I don't
see why it's working even on OSX but not FreeBSD...
Thanks
--
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=39565
Bug ID: 39565
Summary: World of Warships: working in GNU/Linux (Devuan), but
not FreeBSD: out of memory?
Product: Wine
Version: 1.7.53
Hardware: x86
OS: FreeBSD
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mazhe(a)alkumuna.eu
Created attachment 52713
--> https://bugs.winehq.org/attachment.cgi?id=52713
Application error message
I have been able to install and play the game world of warships on GNU/Linux
(Devuan Linux), but copying the wine prefix, I cannot run it on FreeBSD as I am
getting a "out of memory" message.
This is a bit strange, as I should have plenty available... I am using the
packaged version of wine development version.
I've attached the exact program error message and wine trace, if anybody can
give me pointers...
--
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=39347
Bug ID: 39347
Summary: World of Warships 0.4.x/0.5.x: incorrect water surface
height calculated for unknown reasons, causing ships
to appear floating in the air
Product: Wine
Version: 1.7.51
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: focht(a)gmx.net
Distribution: ---
Created attachment 52441
--> https://bugs.winehq.org/attachment.cgi?id=52441
focht's nagato "floating" in port after return from game (water surface level
too low)
Hello folks,
that game got me hooked up at bit (= less time on bugs *g*).
Unfortunately I frequently encounter a nasty in-game bug that surfaces after a
certain amount of time/actions.
I created a support ticket at wargaming.net with screenshots along with some
information.
The ticket hang in pending queue for ~1 week only to be answered by a generic
form "please update your graphics drivers". Oh well.
I mentioned this issue during talks with WineD3D folks at WineConf 2015.
It seems this issue was already known to CodeWeavers (Stefan Doesinger, Matteo
Bruni, Caron Wills).
It's not known yet if this is a Wine bug, a bug with the wargaming engine or
graphics drivers.
There was a hint from Caron to try "low" water rendering setting but I figured
out the bug is present there too but much less noticeable (smaller water
surface "drop" value).
It seems I could force the in-game water surface level drop multiple times by
moving the ship near an island/land mass and then zoom in/zoom out with island
in view (couldn't reproduce consistently though).
If the water drop happened once - it stayed forever - even the ships in port
floated in the air.
Exiting and restarting the client solved the issue.
I encountered the bug with WoWS 0.4.0 upgrade for the first time.
Previous 0.3.x version didn't show it but also crashed more frequently hence
there never was a time when the client ran for consecutive (hour long) game
sessions.
I briefly looked at the game engine and found some game engine locations
related to water rending properties along with their float representations.
Since I didn't want to mess up my account by live-debugging/dumping game engine
data (which could be considered hacking) I refrained from doing further
investigation.
A builtin offline simulation mode would have been nice ... but well.
Tested with recent Wine 1.7.5x version.
Graphics used for testing (all exhibit the same problem):
Intel Haswell HD4600 with FOSS Intel/Mesa:
---- snip ---
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile
OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.6.3
(git-ccef890)
OpenGL core profile shading language version string: 3.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 10.6.3 (git-ccef890)
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 10.6.3 (git-ccef890)
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
OpenGL ES profile extensions:
---- snip ---
NVIDIA GeForce GTX 850M, NVIDIA binary drivers (via optimus):
---- snip ---
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GTX 850M/PCIe/SSE2
OpenGL core profile version string: 4.4.0 NVIDIA 352.21
OpenGL core profile shading language version string: 4.40 NVIDIA via Cg
compiler
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 4.5.0 NVIDIA 352.21
OpenGL shading language version string: 4.50 NVIDIA
OpenGL context flags: (none)
OpenGL profile mask: (none)
OpenGL extensions:
---- snip ---
NVIDIA GeForce GT 425M with FOSS Nouveau/Mesa:
--- snip ---
$ glxinfo | grep -i opengl
OpenGL vendor string: nouveau
OpenGL renderer string: Gallium 0.4 on NVC1
OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.6.3
(git-ccef890)
OpenGL core profile shading language version string: 3.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 10.6.3 (git-ccef890)
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 10.6.3 (git-ccef890)
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
OpenGL ES profile extensions:
--- snip ---
Attached are some screenshots.
Regards
--
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=43785
Bug ID: 43785
Summary: New Critical Error World of Warships 0.6.11
Product: Wine
Version: 2.12
Hardware: Other
OS: Mac OS X
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: captmatt95(a)yahoo.ca
Created attachment 59298
--> https://bugs.winehq.org/attachment.cgi?id=59298
Screen shot of error message.
Game crashes on launch. Recently updated the game to 0.6.11. I have also done
several software updates to see if that was 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.