http://bugs.winehq.org/show_bug.cgi?id=11056
Summary: TAB key counted twice
Product: Wine
Version: 0.9.44.
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: choppy(a)free.fr
In various dialg boxes, the <TAB> key is counted twice, i.e. you're not put on
the next field but on the next-after-next one.
This bug appears in the application NoteWorthy, which is a music score editor.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=33463
Bug #: 33463
Summary: Alan Wake : No sound in cinematics
Product: Wine
Version: 1.5.28
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: xvachon(a)gmail.com
Classification: Unclassified
GOG.com version of the game
Wine 1.5.28
Nvidia hardware
Arch Linux x64
d3dx9_36 override to get around http://bugs.winehq.org/show_bug.cgi?id=31701
There is sound during gameplay, but none in the cinematics. Sound should be
expected at all times.
The log does not show anything related to sound. There is a loop of these two
lines.
fixme:xinput:XInputSetState (0 0x32cd00) Stub!
err:d3d_shader:shader_glsl_select >>>>>>>>>>>>>>>>> GL_INVALID_OPERATION
(0x502) from glUseProgramObjectARB @ ../../../wine/dlls/wined3d/glsl_shader.c /
5829
Which channels should I be looking for to help you debug this?
--
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=40860
Bug ID: 40860
Summary: In Lazarus (for Windows) on Wine, the function keys
F11 and F12 don't work correctly
Product: Wine
Version: 1.8
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ramonrafe(a)gmail.com
Distribution: ---
Problem: In Lazarus (for Windows) on Wine, the function keys F11 and F12 don't
work correctly.
Importance: Normal.
------------------------------------------------------------------------
Hello.
I've installed Lazarus 1.6 for Windows on Wine in Linux Mint 17.
Lazarus compiles well, although the function keys F11 and F12 don't work like
in Windows.
F11 (en Windows) makes visible and active the window with the component
inspector. The cursor goes to the window and the window changes to be on top.
F12 (en Windows) switch betwen the editor of code and the form associated to
that code. The cursor goes to the window and the window changes to be on top.
When F11 or F12 are pressed (in Lazarus on Wine), the cursor goes to the
window, although the window doesn't change to be on top. So, if there are other
windows over it, you won't be able to see the window with the cursor.
It doesn't happen in Windows. In Windows, when you press F11, the window
component inspector pass to be the window with the cursor and the window pass
to be the window on top.
It looks like a minor problem, although this limitation makes Lazarus not
usable in the practice or very unfriendly for use it.
Sorry for my basic English.
Thank you very much.
Ramón.
----------------------------------------------------------------------
Linux Mint: Linux Mint 17 Qiana
Wine: version 1.6 and 1.8 .
Lazarus 1.6:
- File: lazarus-1.6.0-fpc-3.0.0-win32.exe
- Link:
http://sourceforge.net/projects/lazarus/files/Lazarus%20Windows%2032%20bits…
--
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=41664
Bug ID: 41664
Summary: Visual Basic 6.0 fails to show hints while typing
keywords
Product: Wine
Version: 1.8.5
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: rizalmart.98(a)gmail.com
Distribution: ---
When typing functions in visual basic 6.0 like "msgbox(" it does not show any
function hint or guide.
--
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=16574
Summary: Turbocad 7.1 does not display dialog window properly
Product: Wine
Version: 1.1.10
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: tedhansen(a)sasktel.net
Created an attachment (id=18082)
--> (http://bugs.winehq.org/attachment.cgi?id=18082)
terminal messages running turbocad
The "edit entity properties" window in Turbocad 7.1 does not display properly;
the menu bar at the bottom of the window is scaled off to the right so that the
"OK" button is off screen.
--
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=36097
Bug ID: 36097
Summary: valgrind shows leaks in d3d9/stateblock tests on i965
Product: Wine
Version: 1.7.17
Hardware: x86
OS: Linux
Status: NEW
Keywords: download, source, testcase
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: austinenglish(a)gmail.com
Depends on: 36096
Created attachment 48285
--> https://bugs.winehq.org/attachment.cgi?id=48285
valgrind log
==11765== 32,768 bytes in 1 blocks are definitely lost in loss record 787 of
790
==11765== at 0x6F8F6F1: ??? (in /usr/lib/libdrm_intel.so.1.0.0)
==11765== by 0x6F8B378: drm_intel_bo_map (in /usr/lib/libdrm_intel.so.1.0.0)
==11765== by 0x6CBEB10: ??? (in /usr/lib/dri/i965_dri.so)
==11765== by 0x6CBED32: ??? (in /usr/lib/dri/i965_dri.so)
==11765== by 0x6CC2BA1: ??? (in /usr/lib/dri/i965_dri.so)
==11765== by 0x6CE45A3: ??? (in /usr/lib/dri/i965_dri.so)
==11765== by 0x6C833C4: ??? (in /usr/lib/dri/i965_dri.so)
==11765== by 0x65E46BB: ??? (in /usr/lib/libGL.so.1.2.0)
==11765== by 0x65B3E14: ??? (in /usr/lib/libGL.so.1.2.0)
==11765== by 0x5CE995A: create_glxcontext (opengl.c:1254)
==11765== by 0x5CEC2DB: X11DRV_wglCreateContextAttribsARB (opengl.c:2071)
==11765== by 0x5269E0D: wglCreateContextAttribsARB (wgl.c:268)
==11765== by 0x4EABA19: wined3d_caps_gl_ctx_create_attribs (directx.c:300)
==11765== by 0x4EBC4C2: wined3d_adapter_init (directx.c:5178)
==11765== by 0x4EBCA26: wined3d_init (directx.c:5272)
==11765== by 0x4F66387: wined3d_create (wined3d_main.c:105)
==11765== by 0x4E30771: d3d8_init (directx.c:413)
==11765== by 0x4E24804: Direct3DCreate8 (d3d8_main.c:47)
==11765== by 0x497E268: test_state_management (stateblock.c:1801)
==11765== by 0x497E5D0: func_stateblock (stateblock.c:1868)
==11765==
--
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=46251
Bug ID: 46251
Summary: some (all?) crinkler compressed executables crash
because they parse in-memory DLL export tables
Product: Wine
Version: 3.21
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
Assignee: wine-bugs(a)winehq.org
Reporter: p2(a)psychaos.be
Distribution: ---
Created attachment 62950
--> https://bugs.winehq.org/attachment.cgi?id=62950
crash dump and disassembly of decompressor and symbol resolver
Some crinkler compressed executables crash when building the imported symbol
table. The routine which does this relies on parsing the in-memory copy of
KERNEL32.DLL first to retrieve the address for LoadModuleA. This is later used
to load other DLLs. Symbol name matching is done using a hash function. The
executable only stores the hashes of the symbols it wants to import. For each
symbol has in the executable, the symbol resolver routine iterates over all
exported symbol names of the DLL and stores the symbol address if the hashes
match.
The symbol resolver routine crashes because it seems the in-memory copy of
KERNEL32.DLL does not have a exported symbol names table.
Attached:
winhello_asm.txt: the crash dump and a dissassembly of both the decompressor
and the symbol resolver.
winhello.zip: source code for the trivial program, obj file, normally linked
executable (winhello.exe), crinkler linked executable (winhello_cr.exe)_and the
msvcrt.lib as recommended by the crinkler manual. Toolchain used was VS2013
community edition.
crinker can be found here: http://crinkler.net/
--
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=39815
Bug ID: 39815
Summary: BitComet 1.4 crashed on launch
Product: Wine-staging
Version: 1.8-rc4
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: litimetal(a)gmail.com
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
Created attachment 53151
--> https://bugs.winehq.org/attachment.cgi?id=53151
terminal_output.txt
0. Download BitComet(a BitTorrent client) from http://www.bitcomet.com/
$ sha1sum BitComet_1.40_x86_setup.exe
47ebec6261ec6d06c058fc10260016b889478aa5 BitComet_1.40_x86_setup.exe
1. wine BitComet_1.40_x86_setup.exe
You can choose the installer's language
2. cd ~/.wine/drive_c/Program Files/BitComet
wine BitComet.exe
With wine, it works (mostly well)
With wine-staging, it crashed at start up
--
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=46599
Bug ID: 46599
Summary: GNUTLS_PK_ECDSA not found in recent gnutls.h
Product: Wine
Version: 4.1
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: isakov-sl(a)bk.ru
Distribution: ---
Compilation in macOS 10.13.6 with Xcode10.1 and recent gnutls library installed
by MacPort failed with claim that GNUTLS_PK_ECDSA is undefined.
dll/bcrypt/gnutls.c
~~~
#if GNUTLS_VERSION_MAJOR < 3
#define GNUTLS_CIPHER_AES_192_CBC 92
#define GNUTLS_CIPHER_AES_128_GCM 93
#define GNUTLS_CIPHER_AES_256_GCM 94
#define GNUTLS_PK_ECC 4
#define GNUTLS_PK_ECDSA 4
~~~~
But file gnutls.h having version #define GNUTLS_VERSION "3.3.12"
and doesn't contain GNUTLS_PK_ECDSA
so I just replace it by GNUTLS_PK_ECC that has the same value.
I don't know initial idea of (#if GNUTLS_VERSION_MAJOR < 3) so I can't propose
the common patch.
--
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=45599
Bug ID: 45599
Summary: Support for FILE_FLAG_WRITE_THROUGH in CreateFile
breaks Wargaming.net Game Center
Product: Wine-staging
Version: unspecified
Hardware: x86
URL: http://redirect.wargaming.net/WGC/Wargaming_Game_Cente
r_Install_TWA_EU.exe
OS: Linux
Status: NEW
Keywords: download, regression
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dark.shadow4(a)web.de
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
The program closes with the message "Unable to launch the application because
of critical errors."
Guilty patch is
"ml-patches/0027-kernel32-Add-support-for-FILE_FLAG_WRITE_THROUGH-to-.patch" -
reverting it fixes the issue.
To test just run the installer and then run "drive_c/Program
Files/Wargaming.net/GameCenter/wgc.exe" in a fresh(!) WINEPREFIX.
Running the program without the guilty patch, and then with the guilty patch
again seems to fix the issue, also.
--
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=46052
Bug ID: 46052
Summary: Spellforce: regression: black square around mouse
pointer
Product: Wine-staging
Version: 3.18
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 62637
--> https://bugs.winehq.org/attachment.cgi?id=62637
Screenshot.jpeg
After upgrading from wine-staging 3.17 to 3.18, when running Spellforce, I'm
getting black square around mouse cursor. The cursor itself is visible, but it
looks like a texture transparency issue. Black square appears even in main menu
and during starting movies, and it is present during actual gameplay.
If I disable 'Enable CSMT for better graphics performance (deprecated)' in
winecfg, there is a chance that black square doesn't appear right from start,
but it may appear on some cursor change and disappear later, but it's still
pretty reproducible for me. I'm reproducing it with high chance by hovering
over gates to another map.
I've tried running wine-staging 3.17, and couldn't reproduce issue. I've also
tried running wine-vanilla 3.18 and couldn't reproduce issue either.
Native libraries: from d3dx9_24 till d3dx9_43. I've tried clean wine prefix,
issue remained.
Also, I've compared output of wine, and for wine-staging-3.18 I'm getting a lot
of following lines:
003c:fixme:d3d:surface_cpu_blt Unsupported flags 0x80000000.
I didn't get such lines for wine-staging-3.17 or wine-vanilla-3.18.
OS: Gentoo Linux x86_64.
Video driver: nvidia-drivers-387.34
--
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=43891
Bug ID: 43891
Summary: RAGE (Steam) crashes after start in wine-staging
Product: Wine-staging
Version: unspecified
Hardware: x86
URL: http://store.steampowered.com/app/9200/RAGE/
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: gyebro69(a)gmail.com
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
Created attachment 59507
--> https://bugs.winehq.org/attachment.cgi?id=59507
terminal output
The game starts properly in the development version of Wine (2.19), but crashes
in the Staging version (tested with the following Staging versions: 2.10, 2.14,
2.18 and with current Staging-git).
Reproduced the crash with the following Nvidia driver versions: 378.13, 384.59
and with current 387.12.
With nouveau and Mesa 17.2.2 the game crashes in a different way (both in
Staging and the development version), that's probably bug #38969.
The patch in Staging which causes the problem:
https://github.com/wine-compholio/wine-staging/blob/master/patches/opengl32…
Arch Linux x86_64
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GT 730/PCIe/SSE2
OpenGL core profile version string: 4.5.0 NVIDIA 387.12
--
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=45875
Bug ID: 45875
Summary: Desperados: Jerky mouse cursor ingame, ok in menu
(fine in wine-vanilla)
Product: Wine-staging
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: phaidros(a)gmx.at
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
With wine-staging, I get jumping mouse cursor in the game Desperados. The
cursor seems to jump back uncontrollably, which makes the game unplayable.
Interestingly, the cursor works fine in the game main menu. It also works in
the im-game menu (pressing Esc in the game), only in the actual game where the
characters are controlled with the mouse it shows the jerky behaviour.
I get this with wine-staging 3.13, 3.14, 3.15 and 3.16.
Wine-vanilla 3.0, 3.2, and 3.16 does not have this problem, here the mouse
works fine in the menu and in-game.
--
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=40028
Bug ID: 40028
Summary: Tumblebugs 2 crashes with wined3d-csmt.dll, works with
wined3d.dll
Product: Wine-staging
Version: 1.7.54
Hardware: x86
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: isakov-sl(a)bk.ru
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Formerly this game was an indicator for DXTn textures support. It uses DXT5
textures for bugs. So this game some time worked with wine-staging? Not now.
Enable redirect wined3d-csmt.dll
~~~~
fixme:winediag:start_process Wine Staging 1.9.1 is a testing version containing
experimental patches.
fixme:winediag:start_process Please mention your exact version when filing bug
reports on winehq.org.
fixme:ntdll:__syscall_NtCreateNamedPipeFile Message mode not supported, falling
back to byte mode.
fixme:ntdll:__syscall_NtCreateNamedPipeFile Message mode not supported, falling
back to byte mode.
fixme:ntdll:__syscall_NtCreateNamedPipeFile Message mode not supported, falling
back to byte mode.
fixme:ntdll:__syscall_NtCreateNamedPipeFile Message mode not supported, falling
back to byte mode.
fixme:module:load_dll Loader redirect from L"wined3d.dll" to
L"wined3d-csmt.dll"
fixme:winediag:wined3d_dll_init Experimental wined3d CSMT feature is currently
disabled.
fixme:ddraw:DirectDrawEnumerateExA flags 0x00000006 not handled
err:winediag:init_driver_info Invalid GPU override 1002:6740 specified,
ignoring.
fixme:ddraw:ddraw7_Initialize Ignoring guid
{aeb2cdd4-6e41-43ea-941c-8361cc760781}.
err:dbghelp_stabs:stabs_parse Unknown stab type 0x0a
err:dbghelp_stabs:stabs_parse Unknown stab type 0x0a
err:dbghelp_stabs:stabs_parse Unknown stab type 0x0a
err:dbghelp_stabs:stabs_parse Unknown stab type 0x0a
err:dbghelp_stabs:stabs_parse Unknown stab type 0x0a
...
wine: Unhandled exception 0x40000015 in thread 29 at address 0x280bb5d (thread
0029), starting debugger...
~~~
disable
~~~~
fixme:winediag:start_process Wine Staging 1.9.1 is a testing version containing
experimental patches.
fixme:winediag:start_process Please mention your exact version when filing bug
reports on winehq.org.
fixme:ntdll:__syscall_NtCreateNamedPipeFile Message mode not supported, falling
back to byte mode.
fixme:ntdll:__syscall_NtCreateNamedPipeFile Message mode not supported, falling
back to byte mode.
fixme:ntdll:__syscall_NtCreateNamedPipeFile Message mode not supported, falling
back to byte mode.
fixme:ntdll:__syscall_NtCreateNamedPipeFile Message mode not supported, falling
back to byte mode.
fixme:ddraw:DirectDrawEnumerateExA flags 0x00000006 not handled
err:winediag:init_driver_info Invalid GPU override 1002:6740 specified,
ignoring.
fixme:ddraw:ddraw7_Initialize Ignoring guid
{aeb2cdd4-6e41-43ea-941c-8361cc760781}.
fixme:d3d_shader:print_glsl_info_log Info log received from GLSL shader #3:
fixme:d3d_shader:print_glsl_info_log WARNING: Could not find vertex shader
attribute 'vs_in2' to match BindAttributeLocation request.
fixme:ddraw:ddraw_surface7_Flip Ignoring flags 0x1.
fixme:d3d_shader:print_glsl_info_log Info log received from GLSL shader #5:
fixme:d3d_shader:print_glsl_info_log WARNING: Could not find vertex shader
attribute 'vs_in2' to match BindAttributeLocation request.
err:d3d_surface:surface_convert_format Failed to create a destination surface
for conversion.
err:d3d_surface:surface_convert_format Failed to create a destination surface
for conversion.
err:d3d_surface:surface_convert_format Failed to create a destination surface
for conversion.
err:d3d_surface:surface_convert_format Failed to create a destination surface
for conversion.
~~~~
To check if this is my mistake I download ready-to-use WineStage-1.9.1 binary.
Tested also with wine-staging-1.7.54.
Tested wine Crossover 15.0
Same result. The game crashes.
It works with main WineHQ with black insects and balls.
--
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=46608
Bug ID: 46608
Summary: Wine-staging fails to load DLLs on Debian 9 Stretch
Product: Wine-staging
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: larrowe.semaj11(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
When using the official Wine-Staging package for Debian 9 Stretch, there is an
issue where Wine cannot load DLLS. This is definitely a regression from
Wine-Development, where the issue cannot be reproduced.
On an unrelated side note, there appears to be an error while running `wine64
--check-libs` with the same package. After one library is listed, there is a
segmentation vault.
Checked on Wine-Staging 4.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=46104
Bug ID: 46104
Summary: winepulse-PulseAudio_Support patch cause application
to hang with native dsound.dll
Product: Wine-staging
Version: 3.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: lorenzofer(a)live.it
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Hi.
Recently I wanted to play to some old games that were using DirectMusic.
In particular "Imperivm Great Battles of Rome"
So following the procedures I installed the directmusic component and the
native dsound.dll
However when I tried the game I was encountered by an hanged application. (the
application opened it's window and rendered the cursor, but nothing else)
I was on wine-staging as I have some games that require staging patches.
However as I recalled this game worked before, so I tried vanilla wine. It
worked almost flawless (encountering bug Bug 44540 with quartz.dll as native).
Then I tried with older wine-staging version. I started with the wine-staging
3.3 that was the older one in my pacman package cache, and worked flawless.
I then discovered that the first bad wine-staging release is the 3.13 release.
After checking the patch modified between the 3.12 and 3.13 releases, I found
that if I compile wine-staging from source without applying the
winepulse-PulseAudio_Support the issue disappears.
Unfortunatly Imperivm GBR doesn't have an aviable demo, but recently an udated
version was released on steam, and you can ask for a key at FX Interactive for
free. Check the FAQ in the Imperium World forum on Discord.
Normal Log is totally unhelpful as the only thing it give is a:
0009:fixme:thread:create_user_shared_data_thread Creating user shared data
update thread.
Two others affected application are:
Rise of Nation
Rise of Nation Throne and Patriots
Others bug associated with winepulse-PulseAudio_Support and 3.13 Release
(potentially not duplicates):
Bug 45582 - Bug 45623 - Bug 45502
--
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=46587
Bug ID: 46587
Summary: Paint.net v4 crashes with GTK3 Theming
Product: Wine-staging
Version: 4.1
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: toe_head2001(a)yahoo.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 63480
--> https://bugs.winehq.org/attachment.cgi?id=63480
Screenshot showing the EntryPointNotFoundException
It is "Unable to find an entry point named 'BufferedPaintStopAllAnimations' in
DLL 'uxtheme.dll'."
I assume this due to the DLL redirect to uxtheme-gtk.dll from uxtheme.dll.
This crash does not occur when GTK3 Theming is disabled.
--
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=40060
Bug ID: 40060
Summary: Crash dialog button unclickable
Product: Wine-staging
Version: 1.9.2
Hardware: x86
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: isakov-sl(a)bk.ru
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Created attachment 53538
--> https://bugs.winehq.org/attachment.cgi?id=53538
The windows in question
If a game crashes (for example elevated_1024x768.exe) then dialog windows
appeared with two buttons "Show details" and "Close".
These buttons are unclickable because of patch
https://github.com/wine-compholio/wine-staging/blob/master/patches/user32-M…
Reverting the patch resolves 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=45856
Bug ID: 45856
Summary: wine stuck installing python in silent mode
Product: Wine-staging
Version: 3.16
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sbonazzo(a)redhat.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: Fedora
On Fedora 28:
download https://www.python.org/ftp/python/2.7.14/python-2.7.14.msi
$ wine msiexec /i /tmp/python-2.7.14.msi /qn ADDLOCAL=ALL
000b:fixme:winediag:start_process Wine Staging 3.16 is a testing version
containing experimental patches.
000b:fixme:winediag:start_process Please mention your exact version when filing
bug reports on winehq.org.
0028:fixme:dwmapi:DwmIsCompositionEnabled 0x6dc825d4
002d:fixme:iphlpapi:NotifyIpInterfaceChange (family 0, callback 0x69ec7e28,
context 0x91e480, init_notify 0, handle 0x11dfa10): stub
003f:fixme:dwmapi:DwmIsCompositionEnabled 0x6dc825d4
0041:fixme:iphlpapi:NotifyIpInterfaceChange (family 0, callback 0x69ec7e28,
context 0x91e480, init_notify 0, handle 0x11dfa10): stub
wine: configuration in '/home/sbonazzo/.wine' has been updated.
0009:fixme:ntdll:NtLockFile I/O completion on lock not implemented yet
0053:err:msiexec:custom_action_server Failed to create custom action server
pipe: 2
wine get stuck here and doesn't complete the silent install.
Reproducible 100% with wine 3.14-1.fc28 and 3.16-1.fc28
Worked fine in wine 3.8-1.fc28
(https://jenkins.ovirt.org/job/ovirt-guest-agent_master_build-artifacts-fc28…)
--
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=46704
Bug ID: 46704
Summary: League Of Legends 9.4, Connection issue - We're unable
to log you in because you may be offline.
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: werifGX(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 63664
--> https://bugs.winehq.org/attachment.cgi?id=63664
Screenshot of the issue.
League Of Legends (9.4-15540347.15540320) is unable to log-in on wine-4.2
(Staging) with vcrun2017, adobeair and corefonts due "We're unable to log you
in because you may be offline" error
Same problem on Lutris's League Of Legends
(https://lutris.net/games/install/3552/view)
Both of which worked without any noticable issues yesterday (22.02.2019).
Results in : https://i.imgur.com/wIJ4Zit.png
--
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=45578
Bug ID: 45578
Summary: GTA 5 doesn't launch in 3.13, works in 3.12
Product: Wine-staging
Version: 3.13
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: electrodexsnet(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 61994
--> https://bugs.winehq.org/attachment.cgi?id=61994
crash log - crash at line 19,541
I have GTA5 installed in a wine prefix with dxvk. Using wine builtin vulkan
(vulkan-1.dll).
In wine-staging 3.12, GTA 5 runs without issue.
In 3.13, it now hangs at a blank screen after the police siren intro. You can
close it by pressing Alt F4, then Enter. After reverting to 3.12, it works as
expected again.
Versions/System:
GPU: Nvidia GTX 970 | proprietary driver: 396.45
OS: Manjaro stable
DXVK: tested 0.54, 0.63, 0.64 - no difference
winetricks: allfonts, steam
Noteable error messages (line 19,541 in gta5_wine-staging-3.13-crash01):
wine: Unhandled page fault on write access to 0x00000000 at address 0x141275cbc
(thread 013c), starting debugger...
Unhandled exception: page fault on write access to 0x00000000 in 64-bit code
(0x0000000141275cbc).
--
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=46148
Bug ID: 46148
Summary: In World of Warcraft 8 background and water are solid
color and flashes of various color appear many times
per second
Product: Wine-staging
Version: 3.20
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: kgrittn(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
World of Warcraft 8.0.1 (28153)(Release x64)
OS is Ubuntu, both show the same symptoms and were fine before Wine 3.20
(Staging):
Linux kevin-desktop 4.15.0-39-generic #42~16.04.1-Ubuntu SMP Wed Oct 24
17:09:54 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz
16GB
Intel HD Graphics 4000 (Ivybridge) (on motherboard, no expansion slot)
Linux kgrittn-Precision-7720 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2
17:16:02 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
Intel(R) Xeon(R) CPU E3-1505M v6 @ 3.00GHz
32GB RAM
NVIDIA GeForce GTX 470
Symptoms in WoW:
- Backgrounds such as terrain show as a single color (always black?) with no
"litter" or detail -- a roadway looks the same as wild ground which is the same
as the side of a cliff.
- Water shows as a single block of color with no shorline features, reflection,
or transparency to underlying features.
- Random patches of color appear, apparently changing with each screen draw.
- Small animated areas like torch flames show lots of rectangle enclosing the
area with little or none of the normal animation.
--
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=44032
Bug ID: 44032
Summary: Diablo 3 2.6.1: Mouse-downs register as mouse clicks
Product: Wine
Version: 2.20
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sts33nvyb(a)gmail.com
Distribution: ---
Created attachment 59696
--> https://bugs.winehq.org/attachment.cgi?id=59696
Terminal output (not that I expect this to be useful)
In Diablo 3, mouse-downs (pressing and holding the mouse button) often register
as mouse clicks (pressing and immediately releasing the mouse button). This
happens for approximately 50% of the mouse-downs when playing the game, which
dramatically changes how the game plays, since holding down the mouse button is
used for both moving and attacking continuously in the game.
I'm running wine-staging 2.20 on OpenSuse 42.3 x86_64.
This is for the current version of Diablo 3, version 2.6.1.47919 32-bit. Note
that Diablo 3 recently dropped support for Windows XP; since this change,
Diablo 3 no longer works in non-staging wine at all. Also, the 64-bit version
of Diablo 3 has severe performance problems in wine-staging 2.20, so this is
using the 32-bit version of Diablo 3.
I speculate that some bug in wine is causing bogus mouse-up events to sometimes
be generated immediately after mouse-down events.
Note that this is a completely different bug from bug 31262. Note that user
"pakos" has mistakenly commented about this bug in that bug report, dated
2017-11-13. He reports that this problem is present in versions of
wine-staging at least back to 2.5.
There has been some discussion of this bug on the application page. Some users
have reported that changing wine's virtual desktop setting, forcing 32-bit
using setarch, or changing Diablo 3's settings to windowed-fullscreen instead
of fullscreen alleviated the problem. None of these helped for 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.
https://bugs.winehq.org/show_bug.cgi?id=45826
Bug ID: 45826
Summary: Doom 2016 - Rendering issues
Product: Wine-staging
Version: 3.15
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ahmed.com(a)aol.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Created attachment 62283
--> https://bugs.winehq.org/attachment.cgi?id=62283
wine error log
I can't run Doom 2016 with Mesa 18.1.7 or Mesa 18.1.8, so I tried Mesa 18.2.0-1
and the game started but it look so weird, and I can hear the menu sounds but I
can't see the menu.
System information:
Operating system: Manjaro KDE
GPU: AMD HD 8750M
Driver: Mesa 18.2.0-1
Wine version: 3.15 staging-nine
--
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=46224
Bug ID: 46224
Summary: ddraw-Create-rendering-targets-in-video-memory patch
got borked between 3.19 and 3.20
Product: Wine-staging
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sashok.olen(a)gmail.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
Distribution: ---
Testing application - The Sims Complete Collection
With 3.19, the game launches just fine, and I get
`0009:fixme:ddraw:ddraw_surface_create Application wants to create rendering
target in system memory, using video memory instead` fixmes in the terminal
output, and the game starts.
In 3.20, the game aborts the launch, and I don't get the fixmes.
I suspect this rebase might have broke it:
https://github.com/wine-staging/wine-staging/commit/a423a7087ff2dad6f2def0c…
--
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.