http://bugs.winehq.org/show_bug.cgi?id=11991
Summary: Wine Windows OpenGL support regression
Product: Wine
Version: 0.9.57.
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P3
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: imamdxl8805(a)yahoo.com
Dear Wine developers,
This is wine version 0.9.56 and 0.9.57
There are two games that support OpenGL rendering as well as Direct3D redering.
Here are the games:
1. Hitmen 2 Silent Assasin
2. Hitmen 3 Contracts
When I have updated my wine version to 0.9.57, then these games are not playing
anymore with OpenGL rendering. But when I start these games with Direct3D
rendering they are playing fine.
These games played properly with wine version 0.9.55 with OpenGL rendering as
well as Direct3D rendering.
Then I have decided to reinstall wine 0.9.55.
Sorry for the err message printed in the command line. Because I do not have
Internet connection in my home PC.
Best regards,
DXL
--
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=37259
Bug ID: 37259
Summary: Simple Direct2D application fails to work with newer
d3d10_1.dll
Product: Wine
Version: 1.7.26
Hardware: x86
OS: Windows
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: svyatpro(a)gmail.com
BUG: When you run simple Direct2D application (application that I attached
"p010.exe"), Direct2D test fails with newer d3d10_1.dll(Wine 1.7.26) and
doesn't draw anything. When you paste older d3d10_1.dll(Wine 1.7.25) to
\windows\system32 directory, the application p010.exe able to draw simple
vectors but with
error message, that function D3D10CreateStateBlock wasn't found.
Precondition: d2d1.dll, d3d10.dll, d3d10core.dll, d3d10_1.dll, dxgi.dll,
wined3d.dll, libwine.dll should be compiled for Windows and pasted into
\Windows\Sysem32 or to the application environment, real hardware with OpenGL
support seems to be required.
Steps to repro:
1) Run p010.exe app
2) Choose Direct2D
3) Press key with two squares at the left
Expected result: Application should draw simple vectors.
--
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=10643
Summary: WInUAE settings window reappears after being dismissed
Product: Wine
Version: 0.9.50.
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: wine-user
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: markk(a)clara.co.uk
Hi,
WinUAE is an open source (GPL) emulator of Amiga computers. After running
WinUAE and starting the emulation, pressing F12 brings up the settings window.
When this is dismissed by pressing Reset, Quit, Restart, OK, or Cancel, the
window closes and reopens. It should not reopen. That repeats if you press one
of those buttons again. If you press Quit, then Cancel a few times after the
window closes and reopens, the program does eventually quit.
Steps to demonstrate the problem:
(Typical usage of WinUAE involves obtaining an Amiga ROM image file, however it
is possible to use some software without.)
- Download WinUAE 1.4.4 from http://www.winuae.net/. Direct URL for the
installer is http://www.winuae.net/files/InstallWinUAE1440.exe
- Run the installer.
- For an example disk image, you can download e.g.
ftp://ftp.coresystems.de/pub/uae/rsi1.adf.gz
- Start WinUAE. The settings/configuration window appears. Click the "Floppy
drives" entry in the left side of the window, then the "..." button for drive
DF0:. Select the rsi1.adf.gz file.
- Click Start to start emulation.
- Press F12 to bring up the settings window.
- Try to dismiss the window by pressing one of the buttons at the bottom.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=37628
Bug ID: 37628
Summary: Unable To Start Korg Legacy Collection due to Crash in
Authorizer
Product: Wine
Version: 1.7.31
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: tjwebb(a)osakared.com
Distribution: ---
Created attachment 50076
--> https://bugs.winehq.org/attachment.cgi?id=50076
Backtrace from MS-20 Authorizer.exe
Exiting the MS-20 Authorizer.exe, which is triggered by MS-20.exe in any way
(cancel, or entering the license key) causes an attempt to read address 0. The
GUI looks like they used JUCE if that helps. This pretty much prevents me from
even being able to get into the app or even using the plugin.
--
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=39246
Bug ID: 39246
Summary: user32:edit fails in Japanese and Korean locales
Product: Wine
Version: unspecified
Hardware: x86
OS: Windows
Status: NEW
Severity: normal
Priority: P2
Component: user32
Assignee: wine-bugs(a)winehq.org
Reporter: fgouget(a)codeweavers.com
The following error only happens on the WineTest's Japanese and Korean boxes:
edit.c:1521: Test failed: got 1, 1
More specifically one can see this error on the following boxes:
fg-win7u64-1spie9-ja - Japanese locale
fg-win7u64-1spie9-ko - Korean locale
fg-win7u64-1spie9-mx - Japanese locale as far as this test is concerned
newtb-w7u - Japanese locale
This test regression was introduced by the following commit:
commit ba3a6d1f4b9db64c12301d0d83d559dd6f1e83b4
Author: Nikolay Sivov <nsivov(a)codeweavers.com>
Date: Fri Apr 4 21:45:28 2014 +0400
user32: Fix Edit margins calculation for empty client area case.
See:
https://test.winehq.org/data/tests/user32:edit.html
--
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=24644
Summary: AstroburnLite fails to install
Product: Wine
Version: 1.3.4
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: lukasz.wojnilowicz(a)gmail.com
Created an attachment (id=31146)
--> (http://bugs.winehq.org/attachment.cgi?id=31146)
Error message
Steps to reproduce:
1) remove ~/.wine
2) wine AstroburnLite130-0100.exe
Behaviour:
error (see attachment)
Expected behaviour:
Application should start installing
--
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.
http://bugs.winehq.org/show_bug.cgi?id=32106
Bug #: 32106
Summary: Caps Lock doesn't work correctly with WinUAE with
DirectInput
Product: Wine
Version: 1.5.16
Platform: x86-64
URL: http://www.winuae.net/files/InstallWinUAE2410.exe
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: directx-dinput
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: markk(a)clara.co.uk
Classification: Unclassified
Created attachment 42334
--> http://bugs.winehq.org/attachment.cgi?id=42334
Dummy/empty bootable Amiga floppy disk image
This issue shows up with the WinUAE Amiga emulator.
For keyboard and mouse input, WinUAE uses raw input if available, falling back
to DirectInput otherwise. This bug only shows up when WinUAE is using
DirectInput. Raw input was first working in Wine 1.5.16, so if using 1.5.16 or
later, run WinUAE with the -norawinput argument.
Pressing Caps Lock does not affect typed letters properly. For example,
repeatedly mashing the d-f-g letters on the keyboard, and occasionally pressing
Caps Lock might result in something like this (where [CL] denotes Caps Lock
being pressed and released):
gfd [CL] gfd [CL] gFDgFDgFD [CL] GFDGFDGFD [CL] GdGfDGfd [CL] gfdgdgfd [CL]
gFDgdFgdF [CL] GDFGFDGFD [CL] GfdGfDGDf
That should actually look like:
gfd [CL] GFD [CL] gfdgfdgfd [CL] GFDGFDGFD [CL] gdgfdgfd [CL] GFDGDGFD [CL]
gfdgdfgdf [CL] GDFGFDGFD [CL] gfdgfdgdf
I tested using Wine 1.5.16 built from source on Lubuntu 11.10 x86-64.
To reproduce:
- Download and run the WinUAE installer.
- You need to obtain an Amiga ROM image. Try googling for "kick12.rom" OR
"kick13.rom" and you should find the required file easily. Download the file
and copy to a directory accessible by Wine.
- Run wine winuae.exe -norawinput
- When the WinUAE Properties window appears, click ROM under Hardware in the
tree-view at the left side. Click the "..." button to the right of "Main ROM
file" and select the ROM image file.
- Click Floppy drives under Hardware in the tree-view. Click the "..." button
at the upper right of the window to select a floppy disk image. Select the
test.adf file attached to this bug report. (That's a dummy/empty bootable disk;
its only purpose is to leave you in a CLI window where you can type text.)
- Click Start at the bottom of the window. The emulation will start. After a
few seconds you should be presented with a CLI window.
- While mashing various letter keys on the keyboard, press and release Caps
Lock from time to time. Notice the issue described above.
- You can quit WinUAE and run it again without the -norawinput argument.
Repeating the same steps as above, pressing the keys should give the
correct/expected result.
--
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.