wine-bugs January 2008

wine-bugs@winehq.org

1 participants
9873 discussions

[Bug 8683] section sign key input not working in WoW
by wine-bugs＠winehq.org 21 Jan '08

21 Jan '08

http://bugs.winehq.org/show_bug.cgi?id=8683 --- Comment #18 from Dmitry Timoshkov <dmitry(a)codeweavers.com> 2008-01-21 07:30:54 --- (In reply to comment #17) > BTW, just found another bug in this same function. Under the DE layout with > numlock pressed the keypad <.> key generates the VK_SEPARATOR virtualkey, but > this virtualkey is not correctly handled in the function. Seems like it would > need another special numlock case to translate VK_SEPARATOR to KP_Separator, > similar to the cases that already exists for VK_DECIMAL and VK_NUMPAD0 to > VK_NUMPAD9 No, that's a bug in the X11 keyboard layout. I believe that there is a bug in WineHQ bugzilla which already mentions that. -- 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.

1 0

[Bug 8683] section sign key input not working in WoW
by wine-bugs＠winehq.org 21 Jan '08

21 Jan '08

http://bugs.winehq.org/show_bug.cgi?id=8683 --- Comment #17 from Fábio Capela <fabio.capela(a)yahoo.com> 2008-01-21 07:26:15 --- Created an attachment (id=10390) --> (http://bugs.winehq.org/attachment.cgi?id=10390) Another hack, works for some keys but I'm not sure it's the correct approach. Just changing s[2] to s[10] (and the corresponding size field in XLookupString) don't help. I went on and tried to convert the result of XLookupString to wide chars, and it solves the problem for all problematic keys except ß. The changes I used are attached. The only key that is returning a value that needs more than 1 byte is ß, which is exactly the one key that is not working with this newest hack. Not sure why it's not working, it's returning 0x1e9e as the unicode char, but the unicode for ß is 0xdf. BTW, just found another bug in this same function. Under the DE layout with numlock pressed the keypad <.> key generates the VK_SEPARATOR virtualkey, but this virtualkey is not correctly handled in the function. Seems like it would need another special numlock case to translate VK_SEPARATOR to KP_Separator, similar to the cases that already exists for VK_DECIMAL and VK_NUMPAD0 to VK_NUMPAD9 -- 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.

1 0

[Bug 8486] Ulead PhotoImpact 4 fails to start
by wine-bugs＠winehq.org 21 Jan '08

21 Jan '08

http://bugs.winehq.org/show_bug.cgi?id=8486 Jeff Zaroyko <jeffzaroyko(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeffzaroyko(a)gmail.com --- Comment #2 from Jeff Zaroyko <jeffzaroyko(a)gmail.com> 2008-01-21 00:02:35 --- (In reply to comment #0) > Running it puts up a fatal dialog saying > "Unable to read version information from file > C:\\Program Files\\Ulead Systems\\Ulead PhotoImpact\\Iedit.exe, > insufficient memory or system resources low." > > I'll attach a +relay,+ver,+text log. > > (FWIW, this is one of my wife's "must have" apps. > When she got a new windows box recently, she > *went out and bought* an old copy of Photoimpact 4 > on ebay because she missed it so much.) > > I'm cc'ing A.F. on this because he wrote a patch for version.dll > recently (see bug 6393). Dan, Do you still get this message with 0.9.53? I'm looking at another Ulead program DVD Movie Factory 2 SE, it looks like it used to get this message under older wine versions but no longer does. On 0.9.53 I'm investigating a crash in quartz. -- 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.

1 0

[Bug 3930] HOMM shows black screen (sound problem)
by wine-bugs＠winehq.org 21 Jan '08

21 Jan '08

http://bugs.winehq.org/show_bug.cgi?id=3930 --- Comment #22 from Damjan Jovanovic <damjan.jov(a)gmail.com> 2008-01-20 23:10:29 --- Don't include that patch into wine under any circumstances - it's a nasty hack that probably does the wrong thing. Someone who really understands winmm needs to look at this and fix the real problem. Also I need some way to determine which thread the callback is invoked on in Windows XP. -- 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.

1 0

[Bug 11296] New: fixme: msiexeci
by wine-bugs＠winehq.org 21 Jan '08

21 Jan '08

http://bugs.winehq.org/show_bug.cgi?id=11296 Summary: fixme: msiexeci Product: Wine Version: 0.9.52. Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: msi AssignedTo: wine-bugs(a)winehq.org ReportedBy: wolvverine(a)tlen.pl see attachment -- 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.

1 2

[Bug 8683] section sign key input not working in WoW
by wine-bugs＠winehq.org 21 Jan '08

21 Jan '08

http://bugs.winehq.org/show_bug.cgi?id=8683 --- Comment #16 from Dmitry Timoshkov <dmitry(a)codeweavers.com> 2008-01-20 22:56:24 --- Actually char s[2]; may be the bug. Can you see if changing it to char s[10]; helps? -- 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.

1 0

[Bug 8754] Need for Speed Underground doesnt receive keyboard Input
by wine-bugs＠winehq.org 21 Jan '08

21 Jan '08

http://bugs.winehq.org/show_bug.cgi?id=8754 --- Comment #12 from Dave <dave370(a)wix.com.au> 2008-01-20 22:51:24 --- I think the Component for this is wrong. The dll effected by this problem in dinput8 not dinput -- 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.

1 0

[Bug 8683] section sign key input not working in WoW
by wine-bugs＠winehq.org 21 Jan '08

21 Jan '08

http://bugs.winehq.org/show_bug.cgi?id=8683 --- Comment #15 from Fábio Capela <fabio.capela(a)yahoo.com> 2008-01-20 22:46:28 --- Created an attachment (id=10388) --> (http://bugs.winehq.org/attachment.cgi?id=10388) +x11drv,+key,+keyboard,+event trace - game start + pressing the 5 problematic keys (In reply to comment #14) > I'd suggest to generate a +x11drv,+key,+keyboard,+event log and see how > the X11 keyboard layout is being mapped to a vkeys one. This trace is done with my deadkeys patch; I'm at the moment recompiling Wine to get it to the latest git version without any external patches to be able to generate a purer trace if needed, but I don't think it will be needed. In this trace I simply started the game and pressed the 5 problematic keys as seen in my previous post. Not directly related to the trace, but from running xev I've saw a pattern to the problematic keys under the DE layout: every key for which XmbLookupString / XLookupString returns more than 1 byte are not working to bind actions in World of Warcraft. No other keys trigger this bug. For some reason the call to XLookupString inside X11DRV_MapVirtualKeyEx don't seem to be giving the expected result when it should return more than 1 byte, although it's using the correct keycode (i.e., the same reported in the original event). It might be related to the fact that it is storing the character information in a char[2], and then this char array is being returned by X11DRV_MapVirtualKeyEx as an UINT. -- 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.

1 0

[Bug 6437] CUPS Printer-Names are UTF-8, but we handle them as ANSI
by wine-bugs＠winehq.org 21 Jan '08

21 Jan '08

http://bugs.winehq.org/show_bug.cgi?id=6437 --- Comment #5 from Dmitry Timoshkov <dmitry(a)codeweavers.com> 2008-01-20 22:08:11 --- Isn't lpr is run as a native Linux application? Then using CP_ACP is a bug. -- 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.

1 0

[Bug 8683] section sign key input not working in WoW
by wine-bugs＠winehq.org 21 Jan '08

21 Jan '08

http://bugs.winehq.org/show_bug.cgi?id=8683 --- Comment #14 from Dmitry Timoshkov <dmitry(a)codeweavers.com> 2008-01-20 21:31:48 --- I'd suggest to generate a +x11drv,+key,+keyboard,+event log and see how the X11 keyboard layout is being mapped to a vkeys one. -- 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.

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs January 2008