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.
http://bugs.winehq.org/show_bug.cgi?id=34807
Bug #: 34807
Summary: Gruntz crashes on startup in d3d
Product: Wine
Version: 1.7.4
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: jarro.2783(a)gmail.com
Classification: Unclassified
Created attachment 46418
--> http://bugs.winehq.org/attachment.cgi?id=46418
console output of crash
The game Gruntz crashes after playing the first intro video, the backtrace
points to
=>0 0x7e317bb2 wined3d_surface_blt+0x2052() in wined3d (0x00326d58)
further output is attached.
--
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=38766
Bug ID: 38766
Summary: RpcBindingServerFromClient is unimplemented, needed to
determine client Computer Name/IP Address
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: rpc
Assignee: wine-bugs(a)winehq.org
Reporter: mail(a)colinfinck.de
Distribution: ---
Wine's rpcrt4.dll currently doesn't implement the RpcBindingServerFromClient
function.
The following code is the only way I know to determine the Computer Name/IP
Address of the client doing the RPC request:
====================================================================
RpcBindingServerFromClient(NULL, &hServerBinding);
RpcBindingToStringBindingW(hServerBinding, &pwszBinding);
RpcStringBindingParseW(pwszBinding, NULL, NULL, &pwszComputerName, NULL,
NULL);
====================================================================
I either need this function to be implemented or an alternative way to
determine the client's Computer Name/IP Address.
--
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=6682
--- Comment #44 from Fabian Maurer <dark.shadow4(a)web.de> ---
Created attachment 56744
--> https://bugs.winehq.org/attachment.cgi?id=56744
Hack to draw the about dialog properly
I think I found the reason for the wrongly placed textboxes. Attached a hack
that makes it look fine.
We might want to split this issue off though.
If you want to test it yourself, GdiGetCharDimensions gets called at
user32/dialog.c:506
In user32.GdiGetCharDimensions, the very last line:
> return (sz.cx / 26 + 1) / 2;
Here xz.cx is 389, divided by 26 it's 14.96, but it gets truncated to 14. My
hack forces it to round up.
Your thoughts on this?
--
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=31420
Bug #: 31420
Summary: radar opus homeopathic software does not work
Product: Wine
Version: unspecified
Platform: Other
OS/Version: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: faiza_mk(a)hotmail.com
Classification: Unclassified
Created attachment 41301
--> http://bugs.winehq.org/attachment.cgi?id=41301
radar opus does not open install shield shows error
radar opus homeopathic software does not work
--
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=6682
--- Comment #43 from winetest(a)luukku.com ---
(In reply to Fabian Maurer from comment #42)
> Created attachment 56742 [details]
> Wrong placement of labels
>
> The only issue I have, is that the labels are rendered on top of the image,
> what's wrong. But the image always shows, and alt-tab doesn't change that.
I have exactly the same behaviour at Kde but I only tested the version I linked
here today. Just ignore this if I am saying something really stupid. Maybe the
bug is in the textbox (what you call it?) code and not in the patches we
tested.
--
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.