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=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=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=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=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=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=41107
Bug ID: 41107
Summary: Total Commander 8.52a Final has VERY slow folder icons
rendering
Product: Wine
Version: 1.9.16
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: shell32
Assignee: wine-bugs(a)winehq.org
Reporter: katsunori.kumatani(a)gmail.com
Distribution: ---
Created attachment 55313
--> https://bugs.winehq.org/attachment.cgi?id=55313
Terminal Output, not very useful
Using the 32-bit version of Total Commander 8.52a Final (latest non-beta), when
drawing/rendering the icons for folders, it is VERY slow. Download the 32-bit
version here: http://totalcmd2.s3.amazonaws.com/tcmd852ax32.exe
After installing and launching it, please do the following to reproduce:
1) Maximize the Window to have more folders on screen.
2) Near the top-left, to the right of the green "Refresh" button, click on the
"Source: Only file names" button, this enables more folders visible at once to
show the slow effect more.
3) Go/navigate to a folder which has around 200 folders, such as Z:\usr\share
(depends on your Linux distro), it doesn't matter, just make sure it has a lot
of folders to see how painfully slow it is.
This problem of course is not present in Windows.
Terminal output has been attached, however I don't think it has any useful
information because [b]Total Commander version 7 exhibits almost the same
terminal output, but IT IS NOT SLOW like 8.52a![/b] In fact it is almost
instant when rendering folder icons, which look the exact same.
If you turn off folder icons in Preferences, it is fast, so I know that they
are the culprit, 100%.
Btw, the version 9 beta does not seem to have this problem because it uses the
system's folder icons (which are blue on my system) instead of internal. The
internal ones are yellow.
I hope you can track down and fix this bug with this information.
--
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.