wine-bugs October 2016

wine-bugs@winehq.org

1 participants
7784 discussions

[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

[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

[Bug 40958] New: Toontown Rewritten has major lag on wine-staging on FreeBSD and GNOME 3
by wine-bugs＠winehq.org 16 Aug '20

16 Aug '20

https://bugs.winehq.org/show_bug.cgi?id=40958 Bug ID: 40958 Summary: Toontown Rewritten has major lag on wine-staging on FreeBSD and GNOME 3 Product: Wine-staging Version: 1.9.13 Hardware: x86-64 OS: FreeBSD Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: neel(a)neelc.org CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Toontown Rewritten (http://toontownrewritten.com/) has major lag with keystrokes on wine-staging when I use FreeBSD and GNOME 3. TTR is a online game, and using keyboard controls often results in the display lagging by a few seconds. Other desktop environments don't have this lag to as great of an extent (I also tested TTR on Mate and Fluxbox). Is there a reason for 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.

2 4

[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 17124] New: MSYS installer doesn't pop up cmd window?
by wine-bugs＠winehq.org 15 Aug '20

15 Aug '20

http://bugs.winehq.org/show_bug.cgi?id=17124 Summary: MSYS installer doesn't pop up cmd window? Product: Wine Version: 1.1.13 Platform: Other URL: http://www.mingw.org/wiki/msys OS/Version: other Status: NEW Keywords: download, Installer, source Severity: enhancement Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: austinenglish(a)gmail.com When install msys, it floods the terminal with: This is a post install process that will try to normalize betweenyour MinGW install if any as well as your previous MSYS installs if any. I don't have any traps as aborts will not hurt anything.Do you wish to continue with the post install? [yn ] pi.sh: [: ==: unary operator expectedDo you have MinGW installed? [yn ] pi.sh: [: ==: unary operator expectedWhen you install MinGW I suggest you install it to C:/mingw(replace C: with the drive of your choice). Then create an/etc/fstab file with a line that has a value similar to:C:/mingw /mingwPress ENTER to continue Normalizing your MSYS environment.You have script /bin/awkYou have script /bin/cmdYou have script /bin/echoYou have script /bin/egrepYou have script /bin/exYou have script /bin/fgrepYou have script /bin/printfYou have script /bin/pwdYou have script /bin/rviYou have script /bin/rviewYou have script /bin/rvimYou have script /bin/viYou have script /bin/viewMinGW-1.1 has a version of make.exe within it's bin/ directory.Please be sure to rename this file to mingw32-make.exe once youve echo installed MinGW-1.1 because it\s very deficient in function.Press ENTER to continue.C:\msys\1.0\postinstall>pause Press Return key to continue: Towards the end. It looks like something that should be in a cmd prompt (haven't tested on windows yet). The line endings are also wrong, but that's another 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.

2 13

[Bug 38767] New: Naturosoft Pro fails on startup with 'Run-time error 445: Object doesn't support this action' (needs richedit:ITextRange::Paste method implementation)
by wine-bugs＠winehq.org 15 Aug '20

15 Aug '20

https://bugs.winehq.org/show_bug.cgi?id=38767 Bug ID: 38767 Summary: Naturosoft Pro fails on startup with 'Run-time error 445: Object doesn't support this action' (needs richedit:ITextRange::Paste method implementation) Product: Wine Version: 1.7.45 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: richedit Assignee: wine-bugs(a)winehq.org Reporter: bunglehead(a)gmail.com Distribution: --- With bug 37502 fixed next problem is missing Paste() method implementation. -- 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

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