wine-bugs September 2014

wine-bugs@winehq.org

1 participants
9491 discussions

[Bug 23950] New: MPQEdit: Opening a folder results in the wrong error message
by wine-bugs＠winehq.org 27 Aug '20

27 Aug '20

http://bugs.winehq.org/show_bug.cgi?id=23950 Summary: MPQEdit: Opening a folder results in the wrong error message Product: Wine Version: 1.3.0 Platform: x86 URL: http://zezula.net/download/mpqediten32_beta.zip OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: adys.wh(a)gmail.com Attachment #30066 showcases the expected error message ("The system cannot find the path specified"). Instead, running wine mpqedit c:\\ results in "Access denied" error message. -- 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.

2 9

[Bug 30853] New:=?UTF-8?Q?=20Wine=20doesn=E2=80=99t=20always=20handle=20?="right alt" properly
by wine-bugs＠winehq.org 20 Aug '20

20 Aug '20

http://bugs.winehq.org/show_bug.cgi?id=30853 Bug #: 30853 Summary: Wine doesn’t always handle "right alt" properly Product: Wine Version: 1.5.5 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv AssignedTo: wine-bugs(a)winehq.org ReportedBy: sloonz(a)gmail.com Classification: Unclassified Created attachment 40410 --> http://bugs.winehq.org/attachment.cgi?id=40410 workaround/quick and dirty fix I’m trying to get World of Warcraft working under Wine. However, I have huge trouble with key bindings (I use unusual key bindings : I use the right half of my keyboard, whereas most players use the left half). After investigation, I found 3 bugs (different behaviors between Wine and my Windows installation). The first one is the management of the right "Alt" key (labeled "Alt-Gr" on my keyboard). When I press AltGr+l under Windows with Spy++, I get the followings events : <03637> 0007045A P WM_KEYDOWN nVirtKey:VK_CONTROL cRepeat:1 ScanCode:1D fExtended:0 fAltDown:0 fRepeat:0 fUp:0 <03638> 0007045A P WM_KEYDOWN nVirtKey:VK_MENU cRepeat:1 ScanCode:38 fExtended:1 fAltDown:1 fRepeat:0 fUp:0 <03639> 0007045A P WM_KEYDOWN nVirtKey:'L' cRepeat:1 ScanCode:18 fExtended:0 fAltDown:1 fRepeat:0 fUp:0 <03640> 0007045A P WM_DEADCHAR chCharCode:'002F' (47) cRepeat:1 ScanCode:18 fExtended:0 fAltDown:1 fRepeat:0 fUp:0 <03641> 0007045A P WM_KEYUP nVirtKey:'L' cRepeat:1 ScanCode:18 fExtended:0 fAltDown:1 fRepeat:1 fUp:1 <03642> 0007045A P WM_SYSKEYUP nVirtKey:VK_CONTROL cRepeat:1 ScanCode:1D fExtended:0 fAltDown:1 fRepeat:1 fUp:1 <03643> 0007045A P WM_KEYUP nVirtKey:VK_MENU cRepeat:1 ScanCode:38 fExtended:1 fAltDown:0 fRepeat:1 fUp:1 Under Wine 1.5.5 however (WINEDEBUG=+msg), I get those : trace:msg:peek_message got type 7 msg 100 (WM_KEYDOWN) hwnd 0x6007e wp eb lp 760001 [note: wp = VK_OEM_PA2] trace:msg:peek_message got type 7 msg 101 (WM_KEYUP) hwnd 0x6007e wp 4c lp c0260001 [note: wp = 'L'] trace:msg:peek_message got type 7 msg 101 (WM_KEYUP) hwnd 0x6007e wp eb lp c0760001 [note: wp = VK_OEM_PA2] With xev, I get : KeyPress event, serial 93, synthetic NO, window 0x4000001, root 0xbc, subw 0x0, time 5086996, (1585,410), root:(2578,425), state 0x0, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES, XKeysymToKeycode returns keycode: 92 XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 93, synthetic NO, window 0x4000001, root 0xbc, subw 0x0, time 5087052, (1585,410), root:(2578,425), state 0x80, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES, XKeysymToKeycode returns keycode: 92 XLookupString gives 0 bytes: XFilterEvent returns: False After "setxkbmap us", AltGr is bound to Alt_R under X (checked with xev), and I get this under Wine : trace:msg:peek_message got type 7 msg 104 (WM_SYSKEYDOWN) hwnd 0x10046 wp a5 lp 21380001 [wp = VK_RMENU] trace:msg:peek_message got type 7 msg 104 (WM_SYSKEYDOWN) hwnd 0x10046 wp 4c lp 20260001 [wp = 'L'] trace:msg:peek_message got type 6 msg 106 (WM_SYSCHAR) hwnd 0x10046 wp 6c lp 20260001 [wp = 'l'] trace:msg:peek_message got type 7 msg 105 (WM_SYSKEYUP) hwnd 0x10046 wp 4c lp e0260001 [wp = 'L'] trace:msg:peek_message got type 7 msg 101 (WM_KEYUP) hwnd 0x10046 wp a5 lp c1380001 [wp = VK_RMENU] (yes, I have a KEYUP without KEYDOWN) Wich is still not the same as Windows. So I think there is two problems here : - ISO_Level3_Shift is not properly recognized by Wine - "AltGr" doesn't have the same behavior under Wine and Windows FYI, attached patch is a workaround to have the same behavior than Windows. With it, I get this under Wine : trace:msg:peek_message got type 7 msg 100 (WM_KEYDOWN) hwnd 0x10062 wp a2 lp 1d0001 [note: wp = VK_LCONTROL] trace:msg:peek_message got type 7 msg 100 (WM_KEYDOWN) hwnd 0x10062 wp a4 lp 20380001 [note: wp = VK_LMENU] trace:msg:peek_message got type 7 msg 100 (WM_KEYDOWN) hwnd 0x10062 wp 4c lp 20260001 [note: wp = 'L'] trace:msg:peek_message got type 7 msg 101 (WM_KEYUP) hwnd 0x10062 wp 4c lp e0260001 trace:msg:peek_message got type 7 msg 105 (WM_SYSKEYUP) hwnd 0x10062 wp a2 lp e01d0001 trace:msg:peek_message got type 7 msg 101 (WM_KEYUP) hwnd 0x10062 wp a4 lp c0380001 Which is still not the same as Windows : - Windows uses (right) control + menu (with fExtended flag for menu) whereas Wine uses left control + left menu. Not investigated if this is related to TranslateMessage. - AltGr+L is a dead symbol on my keymap. Windows send a DEADCHAR message, wheras Wine send nothing. Note that I had to disable the XFilterEvent test in event.c to have those messages, otherwise nothing is sent to the program (but that’s another story for another bug report) But it suffice for my use case (WoW key bindings with right alt) -- 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.

2 8

[Bug 30193] New: Crysis Wars ded server doesn't resize with wineconsole (curses backend)
by wine-bugs＠winehq.org 19 Aug '20

19 Aug '20

http://bugs.winehq.org/show_bug.cgi?id=30193 Bug #: 30193 Summary: Crysis Wars ded server doesn't resize with wineconsole (curses backend) Product: Wine Version: 1.4-rc6 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: programs AssignedTo: wine-bugs(a)winehq.org ReportedBy: liquitsnake(a)gmx.net Classification: Unclassified Created attachment 39410 --> http://bugs.winehq.org/attachment.cgi?id=39410 screen The Crysis Wars dedicated server, when running under wineconsole with the curses backend, does not resize its viewport. It is stuck at the default 80x25, even if the terminal is considerably larger (see attachment). This produces some unexpected output, as some commands expect a larger size but have to be split over 2 lines via \ My terminal and wineconsole interact just fine, as I have verified with cmd. It's just this app that sticks to 80x25 no matter what. On Windows, it would normally spawn a console window with a size of 132x60 (or less if the desktop resolution can't fit that) Could it be that wineconsole first starts at 80x25 and only later resizes to terminal size? In that case, I can imagine that the app polls the size once during startup and sticks to that, thus limiting itself to 80x25. -- 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.

2 11

[Bug 13624] New: Lineage 2 - The Chaotic Throne - Hellbound
by wine-bugs＠winehq.org 16 Aug '20

16 Aug '20

http://bugs.winehq.org/show_bug.cgi?id=13624 Summary: Lineage 2 - The Chaotic Throne - Hellbound Product: Wine Version: 1.0-rc3 Platform: All OS/Version: other Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: eryk-rutkowski(a)o2.pl Created an attachment (id=13604) --> (http://bugs.winehq.org/attachment.cgi?id=13604) Log from Terminal Problem is in Lineage 2 Hellbound and regarding npkycrypt - dll file. This dll is not work fine and don't recognize keyboard and i can't log in. There is communicate: "The keyboard security module has failed to load. please exit the game and try again" Sorry for my bad english but i'm from other country ;p -- 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.

2 9

[Bug 33317] New: Python error Fatal Python error: buffer overflow in getpathp.c's joinpath() when executing.
by wine-bugs＠winehq.org 15 Aug '20

15 Aug '20

http://bugs.winehq.org/show_bug.cgi?id=33317 Bug #: 33317 Summary: Python error Fatal Python error: buffer overflow in getpathp.c's joinpath() when executing. Product: Wine Version: unspecified Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: andrew.thomas(a)hpcwales.co.uk Classification: Unclassified Created attachment 44067 --> http://bugs.winehq.org/attachment.cgi?id=44067 Lwsn output from running under wine Wine Version : wine64 --version wine-1.5.25 (64 Bit version) GCC Version : gcc --version gcc (GCC) 4.6.2 Python Version : python --version Python 2.7.3 Operating Systems Used: cat /etc/redhat-release Red Hat Enterprise Linux Server release 5.5 (Tikanga) I have also tried on : cat /etc/redhat-release CentOS release 5.5 (Final) Program trying to run lwsn.exe (network render module part of Lightwave : https://www.lightwave3d.com/ ). 30 Day trial available. Command used: wine lwsn.exe -3 -cLWEXT11-64.CFG -d"z:\home\andy.thomas\Atticus" Scenes\black.lws 1 1 Problem, I compiled wine and setup lwsn.exe in accordance with this article: http://lordtangent.blogspot.co.uk/2007/01/running-lightwave-screamernet-lws… Initially it worked fine when running from the command line. I then wrapped it up in a batch script to be sent to our Linux cluster but got a Python error message : Fatal Python error: buffer overflow in getpathp.c's joinpath() I tried to execute interactively on the cluster and this worked fine but when executed from a script it gives the above error. I launched a forum post (as I a haven't done much troubleshooting with wine) : http://forum.winehq.org/viewtopic.php?f=8&t=18632 I have tried the recommendations but had no success. I re-compiled wine with the above gcc compiler and a more up to date version of Python but I can no longer execute on the command line. I now get the Python error regardless of how I execute the command. Any help would be greatly appreciated. If you need any further debugging please let me know. -- 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.

2 10

[Bug 11955] New: NoteTab Pro 5.5 Cursor Display Issue
by wine-bugs＠winehq.org 15 Aug '20

15 Aug '20

http://bugs.winehq.org/show_bug.cgi?id=11955 Summary: NoteTab Pro 5.5 Cursor Display Issue Product: Wine Version: 0.9.57. Platform: PC URL: http://www.notetab.com OS/Version: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: lm_hamilton(a)yahoo.com When the cursor is at the last line of a file and the user presses ENTER to create a new line, it adds the line, but the cursor does not move. If the user starts typing, the text and cursor does go on the last line of the file. I used to have this issue on any file, but for the last several Wine releases, it has only affected outline files. Outlines are just text files with the extension otl. If you open the file in a text editor the topic for each outline starts with H=". I use Slackware 12.0 and Debian. Other users on the Yahoo Group for NoteTab on Linux are using Ubuntu and have the display issue at the top and bottom of the file. I have never had it at the top no matter what I have tried. Following is a text representation of the problem I have, numbers used for lines in the file, and a vertical bar "|" used to show the cursor position after pressing enter to get a new line. 1|Text on line one. 2Line added when press enter. 3Line added when press enter. If you start typing the cursor acts normally and starts adding text at the beginning of the last line added by pressing enter. In this example the text is added after "3". FYI - NoteTab Pro uses a different input control than NoteTab Light or Standard. Light and Standard use richedit. NoteTab is developed in Delphi. I have been a NoteTab user for ten years and beta tester for as long. The anti-cracker controls in NoteTab's trial version may prevent it from working in Wine. -- 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.

2 15

[Bug 34263] New: Framebuffer read-before-write causes graphical glitches
by wine-bugs＠winehq.org 14 Aug '20

14 Aug '20

http://bugs.winehq.org/show_bug.cgi?id=34263 Bug #: 34263 Summary: Framebuffer read-before-write causes graphical glitches Product: Wine Version: 1.7.0 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: achurch+wine(a)achurch.org Classification: Unclassified Created attachment 45608 --> http://bugs.winehq.org/attachment.cgi?id=45608 Suboptimal but functional patch In at least the Final Fantasy XIV: A Realm Reborn character creation benchmark (http://na.finalfantasyxiv.com/benchmark/index.html), framebuffer read-before-write results in graphical glitches such as the entire display or UI overlays flickering or incorrect textures being drawn. This program uses multithreaded rendering (though I don't know whether that's relevant), and in some cases, Direct3D calls which get translated to glBlitFramebuffer() attempt to read from a framebuffer before the GPU has finished rendering to it. The cause was found by dumping OpenGL calls using apitrace (https://github.com/apitrace/apitrace) and observing that replaying the same frame sporadically caused the same sort of glitches as observed in Wine, but the glitches went away when a glFinish() call was inserted at each thread switch. The attached patch fixes these glitches by inserting a glFinish() call before each glBlitFramebuffer() call. This is almost certainly suboptimal, and in my case it causes the benchmark result to drop from ~3500 to ~3000, but it fixes all graphical glitches aside from black squares seen in some cases when the HDR option is enabled in rendering settings. -- 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.

2 17

[Bug 31476] New: Bully: no DirectX 9.0c compatible sound card
by wine-bugs＠winehq.org 14 Aug '20

14 Aug '20

http://bugs.winehq.org/show_bug.cgi?id=31476 Bug #: 31476 Summary: Bully: no DirectX 9.0c compatible sound card Product: Wine Version: 1.5.10 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: marti(a)juffo.org Classification: Unclassified According to the WineHQ entry about "Bully: Scholarship Edition" version 1.2, it used to work in wine 1.3.27. When I try this game on my system, it changes the resolution, displays a loading screen for a moment and then pops up a window saying: Bully: Scholarship Edition requires a DirectX 9.0c compatible sound card to be installed and and configured properly. After clicking "OK", Bully crashes with "Unhandled exception: page fault on read access to 0x00000004". The Bully installer from Steam automatically installs its own copy of DirectX 9. Using wine-1.5.10 on Arch Linux x86_64, with PulseAudio. Sound playback in winecfg and other applications works fine. -- 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.

2 18

[Bug 27207] New: splayer auto quit while open a mp3 file
by wine-bugs＠winehq.org 14 Aug '20

14 Aug '20

http://bugs.winehq.org/show_bug.cgi?id=27207 Summary: splayer auto quit while open a mp3 file Product: Wine Version: 1.3.20 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: fracting(a)gmail.com Created an attachment (id=34764) --> (http://bugs.winehq.org/attachment.cgi?id=34764) Log: $ wine splayer.exe &> wine-splayer.log splayer is an open source player on gpl. http://www.splayer.org/index.en.html 1. Download splayer http://file.splayer.org/avant/SPlayerSetupInt.exe?2124 2. intall cscript.exe with winetricks $ winetricks wsh57 3. install splayer with all default settings. $ wine SetupInt.exe fixme:ole:CoCreateInstance no instance created for interface {a3d8cec0-7e5a-11cf-bbc5-00805f6cef20} of class {bd323430-ce94-11ce-82dd-0800095a5b55}, hres is 0x80004002 Does these fixme harmful? 4. start splayer: $ wine splayer.exe 5. open a mp3 file with splayer, splayer will auto quit with such messages: fixme:gdi:SetColorAdjustment stub fixme:dsalsa:IDsDriverBufferImpl_SetVolumePan (0x2413730,0x208718): stub fixme:dbghelp:elf_search_auxv can't find symbol in module err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr 0x7bc469ec -- 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.

2 17

[Bug 33518] New: Some floors in Star Trek (2013) are completely black
by wine-bugs＠winehq.org 13 Aug '20

13 Aug '20

http://bugs.winehq.org/show_bug.cgi?id=33518 Bug #: 33518 Summary: Some floors in Star Trek (2013) are completely black Product: Wine Version: 1.5.29 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: eurekafag(a)eureka7.ru Classification: Unclassified This is how they look like in the game: http://i.imgur.com/sNy2z7l.png This is how they should look (at least on Xbox360): http://youtu.be/YQCUUcrLfPc?t=30m30s Outdoors and everything else seems to be ok: http://i.imgur.com/Rv2O8sM.png http://i.imgur.com/Ytoi8cC.png I see this repeating message in the terminal: fixme:d3d:resource_check_usage Unhandled usage flags 0x8. Sometimes another message appears: fixme:d3d:wined3d_swapchain_present Ignoring flags 0x80000000. These two spam the output but nothing else appears while playing. I've run the game with WINEDEBUG=+d3d and the resulting file is about 600M long compressed to 23M. Maybe it will help. I launched the game and entered to the buggy room from the screenshot above, then killed it to prevent extra output. -- 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.

2 15

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 September 2014