http://bugs.winehq.org/show_bug.cgi?id=33570
Bug #: 33570
Summary: Mouse Escapes Wine environment in full screen or
windowed mode
Product: Wine
Version: 1.5.29
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: critical
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: luisalvaradox(a)gmail.com
Classification: Unclassified
This started happening around 1.5.25 and since I have checked in 1.5.26 through
1.5.29 for a fix.
The mouse simply escapes the Wine environment in either Window or Full screen
mode.
The game I tested was Swat 4. How to reproduce:
1. Select a map and begin mission.
2. Once in the mission try moving the mouse around. At first sight, it will
look ok but now click on the game or change weapons.
3. Now move the mouse again, you will see it will either escape horizontally,
vertically or both.
Does not matter if you are in Window or Full screen.
Tested on Ubuntu 13.04 64 Bit with Wine 1.5.29
The summary of the bug in the terminal was:
fixme:wininet:query_global_option INTERNET_OPTION_PER_CONNECTION_OPTION stub
fixme:wininet:query_global_option Unhandled dwOption 4
fixme:wininet:query_global_option Unhandled dwOption 5
fixme:wininet:InternetSetOptionExA Flags 00000000 ignored
fixme:wininet:InternetSetOptionExA Flags 00000000 ignored
fixme:wininet:InternetSetOptionW
INTERNET_OPTION_SEND/RECEIVE_TIMEOUT/DATA_SEND_TIMEOUT 20000
fixme:wininet:InternetSetOptionExA Flags 00000000 ignored
fixme:wininet:InternetSetOptionW
INTERNET_OPTION_SEND/RECEIVE_TIMEOUT/DATA_SEND_TIMEOUT 20000
fixme:process:GetProcessWorkingSetSize (0xffffffff,0x43eab4,0x43eab0): stub
fixme:win:EnumDisplayDevicesW ((null),0,0x43e5e8,0x00000000), stub!
fixme:wbemprox:client_security_SetBlanket 0x7d20cfb8, 0x142de8, 10, 0, (null),
3, 3, (nil), 0x00000000
fixme:wbemprox:client_security_Release 0x7d20cfb8
fixme:wbemprox:wbem_services_CreateInstanceEnum unsupported flags 0x00000030
fixme:win:EnumDisplayDevicesW ((null),0,0x43d9a8,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x43e698,0x00000000), stub!
---------------------------
Havok - Build (20031208)
Base system initialized.
----------------------------
fixme:system:SystemParametersInfoW Unimplemented action: 59 (SPI_SETSTICKYKEYS)
fixme:win:EnumDisplayDevicesW ((null),0,0x43cba8,0x00000000), stub!
fixme:d3d:wined3d_swapchain_set_gamma_ramp Ignoring flags 0x1.
fixme:d3d:wined3d_swapchain_set_gamma_ramp Ignoring flags 0x1.
err:ole:CoGetClassObject class {41b89b6b-9399-11d2-9623-00c04f8ee628} not
registered
err:ole:CoGetClassObject class {41b89b6b-9399-11d2-9623-00c04f8ee628} not
registered
err:ole:create_server class {41b89b6b-9399-11d2-9623-00c04f8ee628} not
registered
err:ole:CoGetClassObject no class object {41b89b6b-9399-11d2-9623-00c04f8ee628}
could be created for context 0x7
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d9:Direct3DShaderValidatorCreate9 stub
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:imm:ImmReleaseContext (0x100f0, 0x672c7fe8): stub
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
--
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=41708
Bug ID: 41708
Summary: Duo 0.10 crashes on startup
Product: Wine
Version: 1.9.23
Hardware: x86-64
URL: http://duo.tuxfamily.org/
OS: Mac OS X
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: tobbi.bugs(a)googlemail.com
Created attachment 56116
--> https://bugs.winehq.org/attachment.cgi?id=56116
backtrace
Download:
http://download.tuxfamily.org/duo/duo-0.10_win32_install.exe
Hash:
SHA1(duo-0.10_win32_install.exe)= 0725af5b0dd7e9332367707dad7677d35612f7f1
Steps to reproduce:
1. Install program using installation assistant.
2. Try to start it. You keep getting a crash. Crash report attached.
--
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=24718
Summary: Condes does not work under wine
Product: WineHQ Apps Database
Version: unspecified
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: appdb-unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: mihai.ibanescu(a)gmail.com
Condes (http://www.condes.net) is an orienteering mapping application. It would
be awesome if it ran under wine. It installs and launches, but the map is
rendered wrong - every line or point is 100x (rough guess :-) thicker than it
should be.
>From a discussion with the developer, who was very interested in getting the
app to run under wine:
<quote>
I don't know if you have any contacts to the wine people, but if you allude to
them that I use so-called MapMode MM_ANISOTROPIC, and that I manipulate
ViewportExtent in order to achieve the correct "zoom" level, then perhaps that
might ring a bell with them.. (there are more "modern" means of transforming
the coordinate system than what I use, but those means won't work on Win 9x, so
as long as I have to keep supporting Win9x, I'll have to stick with the archaic
fashion of coordinate system manipulation)
</quote>
To install the app to reproduce the problem, here is the link to download it:
http://www.condes.net/ver8/install_condes8.exe
You do not need to register the app, the problem shows up even in the trial
version. After it launches, what should be a map is a big conglomeration of
thick lines.
I know nothing about Windows, so it's probably hard for me to help right off
the bat, but if what Finn says in the quote above rings a bell to anyone, I
could try to dedicate it some time.
Thank you!
--
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=7592
Alexandre Julliard <julliard(a)winehq.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |CLOSED
--- Comment #24 from Alexandre Julliard <julliard(a)winehq.org> ---
Closing bugs fixed in 2.0-rc4.
--
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=42074
Bug ID: 42074
Summary: osu! - Audio latency regression (ALSA)
Product: Wine
Version: 2.0-rc3
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: yalterz(a)gmail.com
Distribution: ---
Introduced in wine 1.9.10, still present in 2.0-rc3. Copying my description
from a comment on another issue.
Hello, I'd like to describe my experience with the added sound latency. I'm the
author of https://bugs.winehq.org/show_bug.cgi?id=40716
I'm using ALSA (no PulseAudio), with patched winealsa.drv for reduced latency.
The patch is simply changing three constants at the top of mmdevdrv.c
(DefaultPeriod, MinimumPeriod, EXTRA_SAFE_RT) to lower values (the ones that
work for me: 22000, 22000, 11000 respectively).
On wine 1.9.9 and earlier where everything works fine, this results in an
extremely low (almost none) audio latency, which is good. Reducing
DefaultPeriod and MinimumPeriod lower makes the sound crackle a lot. Reducing
EXTRA_SAFE_RT doesn't seem to change anything.
On wine 1.9.10 and above the "minimal" values of the constants seem to be
around 10000 and 10000 for me, below that there's no sound at all (there's no
crackling stage). The audio latency is much higher (both on "good" values from
wine 1.9.9 and on the new minimal values) which makes the game feel much worse.
Arch Linux x64
32-bit wine prefix
--
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=35700
Bug ID: 35700
Summary: Arabic Shaping Is Broken After Rechedit News.
Product: Wine
Version: 1.7.13
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: richedit
Assignee: wine-bugs(a)winehq.org
Reporter: moceap(a)hotmail.com
I update my Wine from 1.7.8 to 1.7.13 ::
Saping of Arabic full failed !!
In 1.7.8 I have just this bug34513
--
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=35293
Bug ID: 35293
Summary: Halo: CE, glPointSize error = INVALID_VALUE
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: kierek93(a)gmail.com
Classification: Unclassified
Created attachment 47069
--> http://bugs.winehq.org/attachment.cgi?id=47069
log
For about half year I'm struggling to get Halo: Combat Evolved run without
graphical bugs in wine, but I just couldn't think of anything, so I came to a
conclusion that it can be a bug in Mesa. I filled mesa bug, but someone there
said, that it sounds like bug in wine3d, so here I am.
My Spec:
Manjaro Linux
Intel i3-3110m (with intel hd graphics 4000)
Kernel 3.12.6
KDE 4.12
Mesa 10.0.1(didn't work with 9.2)
Wine 1.6 (the same with 1.7.9)
The game itself starts fine, but with horrible graphical glitches, and terminal
getting spammed by glPointSize errors.
Here you can see screenshots:
https://www.dropbox.com/s/f9vik5w6e2v9w1r/zrzut%20ekranu11.pnghttps://www.dropbox.com/s/gbd5jg7rbqxvbvi/zrzut%20ekranu12.png
Because of these glitches, the game is unplayable, but as you can see on the
second screenshot, it's (technically) playable.
When I was on nvidia hardware, and using nvidia blob, the game was perfectly
playable, so I think that the problem is with compatibility somewhere between
wine, mesa and intel drivers.
--
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=42057
Bug ID: 42057
Summary: Pressing Ctrl+C to close iTunes results in error
dialog with gibberish title
Product: Wine
Version: 2.0-rc2
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: msvcrt
Assignee: wine-bugs(a)winehq.org
Reporter: alexhenrie24(a)gmail.com
Distribution: ---
Created attachment 56544
--> https://bugs.winehq.org/attachment.cgi?id=56544
screenshot
To reproduce:
1. Install iTunes.
2. Start iTunes from a terminal, `wine 'C:\Program Files\iTunes\iTunes.exe'`.
3. Go back to the terminal and press Ctrl+C to exit iTunes.
An error dialog appears, which is understandable because iTunes was not
designed to be closed in this way, but the dialog title should be legible. A
screenshot is attached.
--
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=41347
Bug ID: 41347
Summary: TMIDI Player: Some characters and logos in LCD are
rendered as black rectangles
Product: Wine
Version: 1.9.19
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdi32
Assignee: wine-bugs(a)winehq.org
Reporter: kakurasan(a)gmail.com
CC: julliard(a)winehq.org
Regression SHA1: b81a7d976e3c3de36a01401d125871d3014e6c67
Distribution: ---
Created attachment 55695
--> https://bugs.winehq.org/attachment.cgi?id=55695
Screenshot (Wine 1.9.19)
Some characters (number characters, ':', '/') and logos (XG, GENERAL MIDI, GS)
in LCD are rendered as black rectangles.
Download (Japanese): http://hp.vector.co.jp/authors/VA010012/
----- Result of regression testing -----
b81a7d976e3c3de36a01401d125871d3014e6c67 is the first bad commit
commit b81a7d976e3c3de36a01401d125871d3014e6c67
Author: Alexandre Julliard <julliard(a)winehq.org>
Date: Fri May 25 11:47:46 2012 +0200
gdi32: Always use the DIB engine for monochrome bitmap rendering.
:040000 040000 feafcbbcb88944b1f24f7a41555876f66db37167
56c006bf256eab577327225e165bf59c06fc04c9 M dlls
--
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=40169
Bug ID: 40169
Summary: Recognize INTERNET_FLAG_SECURE with
INTERNET_INVALID_PORT_NUMBER in GetHttpConnection
Product: Wine
Version: 1.9.3
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wininet
Assignee: wine-bugs(a)winehq.org
Reporter: PhoneixSegovia(a)gmail.com
Distribution: ---
When using GetHttpConnection with the port INTERNET_INVALID_PORT_NUMBER and the
flag INTERNET_FLAG_SECURE wininet interpret incorrectly and try to connect to
port 80.
For example this is the code used in the windows program to make a request:
#include "afxinet.h"
BOOL servicioPost(const char* actionPage, CString& strFormData, CString&
mensajeError, CString& contenidoFichero){
CString strHeaders = _T("Content-Type: application/x-www-form-urlencoded");
CHttpConnection* pConnection = NULL;
CHttpFile* pFile = NULL;
BOOL retorno = FALSE;
TRY{
CInternetSession session;
pConnection = session.GetHttpConnection(DOMINIO_SERVIDOR,
INTERNET_FLAG_SECURE,INTERNET_INVALID_PORT_NUMBER, NULL, NULL);
if (pConnection){
pFile = pConnection->OpenRequest(CHttpConnection::HTTP_VERB_POST,
actionPage, NULL, 1, NULL, NULL, INTERNET_FLAG_SECURE);
if (pFile){
if (pFile->SendRequest(strHeaders,
(LPVOID)(LPCTSTR)strFormData, strFormData.GetLength())){
retorno = TRUE;
// Make another stuff
}
}
}
}
CATCH_ALL(e){
char mensaje[100];
e->GetErrorMessage(mensaje, 100);
mensajeError = "Error Wininet: ";
mensajeError += mensaje;
}
END_CATCH_ALL
if (pConnection)delete pConnection;//don't skip
if (pFile)delete pFile;//don't skip
return retorno;
}
--
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.