wine-bugs December 2017

wine-bugs@winehq.org

1 participants
7830 discussions

[Bug 44200] New: Quake Champions Instant Crash To Desktop (Steam)
by wine-bugs＠winehq.org 28 Aug '20

28 Aug '20

https://bugs.winehq.org/show_bug.cgi?id=44200 Bug ID: 44200 Summary: Quake Champions Instant Crash To Desktop (Steam) Product: Wine Version: 2.21 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: 7oxicshadow(a)googlemail.com Distribution: --- Created attachment 59969 --> https://bugs.winehq.org/attachment.cgi?id=59969 QC crash dump I have been playing Quake Champions in Wine with no problems for the past few months but unfortunately there was a patch released in December that broke compatibility. If you open the game, a black window opens and just before the intro would start to play the game crashes back to desktop. This issue is/was present for a large number of real windows 7 users as well. A solution was posted on the Quake Champions forum which has fixed the problem for %95 of the community. 1. Make sure that Win 7 SP1 is installed 2. Install the following (specific) windows update: https://www.microsoft.com/en-us/download/details.aspx?id=36805 Does anyone know what this update does, Is there anyway to install it on Wine? There is no useful debug information as it crashes silently but I have attached a crashdump.dmp file. I am unsure if the format is propitiatory or not. I have tested both 2.21 and 2.21 staging as both were working fine before the patch. The following link contains an image of a decoded crash dump: https://bethesda.net/community/topic/148801/quake-champions-failed-to-launc… The general consensus is that it is something related to game overlays as the issue has been linked to plays.tv and a number of graphics card software overlays -- 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 7

[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 43203] New: Crashing Devil Mac Cry 5
by wine-bugs＠winehq.org 28 Aug '20

28 Aug '20

https://bugs.winehq.org/show_bug.cgi?id=43203 Bug ID: 43203 Summary: Crashing Devil Mac Cry 5 Product: Wine-staging Version: 2.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: tall89(a)mail.ru CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- WINEDEBUG=fixme-all,err+loaddll,err+dll,err+file,err+reg ------ Program jamp.exe ------ err:seh:setup_exception_record stack overflow 1312 bytes in thread 014b eip 7bc68356 esp 01330e10 stack 0x1330000-0x1331000-0x1b30000 -- 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 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 44197] New: Microsoft Streets and Trips 2006 Crashes on startup and in Find
by wine-bugs＠winehq.org 25 Aug '20

25 Aug '20

https://bugs.winehq.org/show_bug.cgi?id=44197 Bug ID: 44197 Summary: Microsoft Streets and Trips 2006 Crashes on startup and in Find Product: Wine Version: 3.0-rc2 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: jpleonard12(a)gmail.com Distribution: --- Microsoft Streets and Trips crashes several times on startup before it works. Using the 'Find' toolbar causes the application to crash and restart. -- 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 42436] New: Wine Wiki: Building Wine - Memory & Address Checkers
by wine-bugs＠winehq.org 22 Aug '20

22 Aug '20

https://bugs.winehq.org/show_bug.cgi?id=42436 Bug ID: 42436 Summary: Wine Wiki: Building Wine - Memory & Address Checkers 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: wylda(a)volny.cz Distribution: --- I don't know, if anyone tried recently follow wiki link: https://wiki.winehq.org/Building_Wine#Memory_.26_Address_Checkers This link mentions "...you only need to pass the -fsanitize=address flag to the compiler when building" ../wine-source/configure CFLAGS="-g -O1 -fsanitize=address -other-flags" But this fails soon in make_xftmpl.o: In function fatal_error': ..../tools/make_xftmpl.c:116: undefined reference to `__asan_option_detect_stack_use_after_return' ..../tools/make_xftmpl.c:116: undefined reference to `__asan_stack_malloc_1' Passing LIBS="-lasan" to configure fixes this, but build fails anyway at cca 63%: ..../dlls/ntdll/loader.c:2979: undefined reference to `pthread_sigmask' Per some gentoo wiki: Some configure scripts test the need of the -lpthread compiler flag by testing whether the function pthread_create() is available without it. The Address Sanitizer library (libasan) provides this function. However it does not have a full pthread implementation, more advanced pthread functions aren't provided. Therefore the compilation fails. A workaround is to add the -lpthread compiler flag manually. Passing LIBS="-lasan -lpthread" to configure fixes this issue, but anyway fails at the end: ../tools/sfnt2fon/sfnt2fon -o coue1255.fon ../../wine_git_src/fonts/courier.ttf -d 128 13,1255,8 Makefile:174: recipe for target 'coue1255.fon' failed ==16755==ASan runtime does not come first in initial library list; you should either link runtime to your application or manually preload it with LD_PRELOAD. make[1]: *** [coue1255.fon] Error 1 make: *** [fonts] Error 2 Did anyone tried to follow that Wiki? I tried that on Debian Stretch. Gcc (Debian 6.3.0-6) 6.3.0 20170205 -- 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 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 41000] New: wineconsole curses backend 64bit: Some uppercase chars broken on Crysis Wars Dedicated Server
by wine-bugs＠winehq.org 19 Aug '20

19 Aug '20

https://bugs.winehq.org/show_bug.cgi?id=41000 Bug ID: 41000 Summary: wineconsole curses backend 64bit: Some uppercase chars broken on Crysis Wars Dedicated Server Product: Wine Version: 1.9.14 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: programs Assignee: wine-bugs(a)winehq.org Reporter: main.haarp(a)gmail.com Distribution: --- I am running the Crysis Wars Dedicated Server in wineconsole. The server offers both 32bit and 64bit binaries. Using wineconsole's user backend, both 32 and 64bit work fine. Using the curses backend, 32bit works fine. 64bit however experiences a bug. Some uppercase characters cannot be typed or pasted at all. There is no reaction. wineconsole will display them just fine, but simply will not let them be typed. The affected chars are uppercase versions of these: 2 4 6 0 - f h j k ; [] q r t y o p x c v m , . / (assuming US keyboard layout) -- 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

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 December 2017