wine-bugs June 2016

wine-bugs@winehq.org

1 participants
7703 discussions

[Bug 37913] New: Inconsistent rounding behaviour for sprintf
by wine-bugs＠winehq.org 28 Aug '20

28 Aug '20

https://bugs.winehq.org/show_bug.cgi?id=37913 Bug ID: 37913 Summary: Inconsistent rounding behaviour for sprintf Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: msvcp Assignee: wine-bugs(a)winehq.org Reporter: christopherwuy(a)gmail.com Distribution: --- sample source code and output demonstrating the problem: #include <iostream> #include <stdio.h> using namespace std; int main() { double a; a = 3.5; char *tmp = new char(100); char fmt[18] = " is %.0f"; sprintf(tmp, fmt, a); cout<<endl<<a<<tmp<<endl<<endl; a = -4.5; sprintf(tmp, fmt, a); cout<<endl<<a<<tmp<<endl<<endl; a = -0.5; sprintf(tmp, fmt, a); cout<<endl<<a<<tmp<<endl<<endl; a = 2597.625; printf("%.3f", a); sprintf(tmp, " is %.2lf", a); cout<<tmp<<endl<<endl; } This code running by wine 's Output is: 3.5 is 4 -4.5 is -4 -0.5 is -0 2597.625 is 2597.62 while windows' output is: 3.5 is 4 -4.5 is -5 -0.5 is -1 2597.625 is 2597.63 It indicated that Wine's sprintf used rounding rule which is Round half to even, while windows used Round half away from zero. You can find a detailed discussion of 'similar bug' form https://sourceware.org/bugzilla/show_bug.cgi?id=4943 -- 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 24320] New: Unexpected DetectEnvStatus.exe crash with Cisco Quick VPN Client (QVPN 1.4.1.2)
by wine-bugs＠winehq.org 28 Aug '20

28 Aug '20

http://bugs.winehq.org/show_bug.cgi?id=24320 Summary: Unexpected DetectEnvStatus.exe crash with Cisco Quick VPN Client (QVPN 1.4.1.2) Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: ethanfharris(a)gmail.com Cisco QVPN v1.4.1.2 does not work under Wine. QVPN is used to establish an IPSec Virtual Private Network tunnel from a client computer to a Cisco Router/Gateway to facilitate secure communication over the internet. There appear to be 3 errors when running the Cisco QVPN application under Wine: (a) an apparent crash / closure of DetectEnvStatus.exe (b) a failure to resolve a DDNS domain name, and (c) QVPN is not able to ping the gateway router, and all data transfer over the VPN fails. In all cases a popup box appears (see attached screenshot) indicating that DectectEnvStatus.exe has a serious problem and has closed. If anyone wants to debug this, I can supply a copy of QVPN, and I can set up a temporary guest account on my WRVS4400N small business router for testing purposes. QVPN works fine under Windows Vista SP2, and works fine on a Ununtu 10.04LTS host with a Vista guest running under Oracle VirtualBox. So the QVPN application itself is OK, and the problem is related somehow to Wine or various underlying services. On the attached screenshot the DetectEnvStatus popup appears immediately when I attempt to connect the VPN. If I use the IP address of the gateway router I am connecting to in lieu of the DDNS domain name, QVPN will create the VPN, but the tunnel verification ping test fails and the tunnel will not transmit data, which is why the "remote gateway not responding" message also appears on the screenshot. If I specify the DDNS domain name of the remote gateway router, the VPN tunnel is not established (not shown), suggesting a dynamic DNS name-to-IP address resolution related problem in Wine. Any help would be appreciated. -- 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 13

[Bug 39881] New: d3dx9_36/tests/mesh.ok: failed on line 4145 Test text
by wine-bugs＠winehq.org 28 Aug '20

28 Aug '20

https://bugs.winehq.org/show_bug.cgi?id=39881 Bug ID: 39881 Summary: d3dx9_36/tests/mesh.ok: failed on line 4145 Test text Product: Wine Version: 1.9.0 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3dx9 Assignee: wine-bugs(a)winehq.org Reporter: litimetal(a)gmail.com Distribution: --- Created attachment 53245 --> https://bugs.winehq.org/attachment.cgi?id=53245 terminal_output.txt run $ make mesh.ok, got mesh.c:4145: Test failed: Test text ('wine', 1.000000, 0.000000), glyph 4, face 280 normal, result (0, -0, -1), expected (0, 0, 1) Is this related to bug 28810? -- 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 4

[Bug 39712] New: AirDC++: Crash after finishing setup wizard
by wine-bugs＠winehq.org 28 Aug '20

28 Aug '20

https://bugs.winehq.org/show_bug.cgi?id=39712 Bug ID: 39712 Summary: AirDC++: Crash after finishing setup wizard Product: Wine Version: 1.8-rc2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: archee(a)tuta.io Distribution: --- Created attachment 52965 --> https://bugs.winehq.org/attachment.cgi?id=52965 wine terminal output In the setup wizard, when it says "The wizard has completed successfully", then press Cancel (Next doesn't work), now it will show splash screen and then a dialog "AirDC++ just encountered a fatal bug and should have written exceptioninfo.txt the same directory as the executable" Download: https://github.com/airdcpp/airgit/releases/download/3.00/AirDC_Installer_3.… $ sha1sum AirDC_Installer_3.00.exe bdaef50c9388135b9e326ea03118a1254f2ecd82 AirDC_Installer_3.00.exe -- 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 6

[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 39380] New: test.winehq.org: Provide a way to know why a report was rejected
by wine-bugs＠winehq.org 22 Aug '20

22 Aug '20

https://bugs.winehq.org/show_bug.cgi?id=39380 Bug ID: 39380 Summary: test.winehq.org: Provide a way to know why a report was rejected Product: WineHQ.org Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: www-unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- When WineTest submits a report that report can get thrown away. Either because it's too big, because it has too many failures, because too many tests were skipped or because of other reasons unknown. The WineTest.exe is never notified of this because the report analysis is run asynchronously with respect tot he submission process. But annoyingly there is no way for the submitter to know why the report was rejected even later, levaing him to guess as to what needs fixing. One way to plug this hole would be to send an email with the reason to the address field in the report. But that could probably be abused to send emails to arbitrary persons. A very simple alternative would be to create a per-commit text file containing one line per ignored report with the report's tag, timestamp of when it was analyzed and the reason why it was ignored. -- 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 5

[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 37928] New: Photoshop CS6: Mini-bridge panel does not show directory entries in alphabetical order
by wine-bugs＠winehq.org 19 Aug '20

19 Aug '20

https://bugs.winehq.org/show_bug.cgi?id=37928 Bug ID: 37928 Summary: Photoshop CS6: Mini-bridge panel does not show directory entries in alphabetical order Product: Wine Version: 1.7.34 Hardware: arm OS: Linux Status: UNCONFIRMED Severity: normal Priority: P3 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: robert.munteanu(a)gmail.com Distribution: --- Steps to reproduce: 1. Launch Photoshop 2. Click File -> Open in mini bridge 3. Navigate to a folder with multiple subfolders The subfolders are not ordered alphabetically, but in an apparently random manner. They are definitely not ordered by creation date ( I created the situation in my screenshot using a simple "mkdir a b c d e f g h i j k l" . -- 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 6

[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

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 June 2016