August 2019 - Wine-bugs - list.winehq.org

[Bug 46912] New: Mesa3D don't working in Wine
by wine-bugs＠winehq.org 28 Aug '20

28 Aug '20

https://bugs.winehq.org/show_bug.cgi?id=46912 Bug ID: 46912 Summary: Mesa3D don't working in Wine Product: Wine Version: 3.0 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: opengl Assignee: wine-bugs(a)winehq.org Reporter: sk9258user(a)mail.ru Distribution: --- I have an Exagear Windows version 3.0.1 program with pure Wine 3.0 stable (x86). Everything works except programs 3d. Linux Ubuntu 14.04 image that is in the x86 emulator already has Mesa installed, but for some reason it does not transfer OpenGL to Wine. I tried to install Mesa3D (for Windows) in system32 - it does not work, to folder with the game - it does not work, with prefix -opengl in the startup command - it does not work. Help with this, I really need 3D programs on my Android phone without OpenGL videocard. -- 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 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 47515] New: Wineserver Wiki page contains broken links to Wineserver manpage
by wine-bugs＠winehq.org 23 Aug '20

23 Aug '20

https://bugs.winehq.org/show_bug.cgi?id=47515 Bug ID: 47515 Summary: Wineserver Wiki page contains broken links to Wineserver manpage Product: WineHQ.org Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: www-unknown Assignee: wine-bugs(a)winehq.org Reporter: newbie13xd(a)gmail.com Distribution: --- This page contains two links to the Wineserver manpage, however both are broken. Aside from this, it contains the text "{{{server/protocol.def}}}", which I assume is meant to be a link. Here is the link: https://wiki.winehq.org/Wineserver -- 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 23 Aug '20

23 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 46446] New: Value for WM_KEYLAST too low in https://wiki.winehq.org/ List_Of_Windows_Messages
by wine-bugs＠winehq.org 23 Aug '20

23 Aug '20

https://bugs.winehq.org/show_bug.cgi?id=46446 Bug ID: 46446 Summary: Value for WM_KEYLAST too low in https://wiki.winehq.org/List_Of_Windows_Messages Product: WineHQ.org Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: www-unknown Assignee: wine-bugs(a)winehq.org Reporter: jeroen.bugs.winehq.org(a)pluimers.com Distribution: --- Value for WM_KEYLAST is 0x0108 (264) but should be 0x0109 (265) as the range Value for WM_KEYFIRST .. WM_KEYLAST should include WM_UNICHAR which correctly has value 0x0109 (265) as per https://docs.microsoft.com/en-us/windows/desktop/inputdev/wm-unichar -- 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 3

[Bug 39380] New: test.winehq.org: Provide a way to know why a report was rejected
by wine-bugs＠winehq.org 23 Aug '20

23 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 47604] New: Cannot use the app
by wine-bugs＠winehq.org 19 Aug '20

19 Aug '20

https://bugs.winehq.org/show_bug.cgi?id=47604 Bug ID: 47604 Summary: Cannot use the app Product: Packaging Version: unspecified Hardware: aarch64 OS: Android Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-packages Assignee: wine-bugs(a)winehq.org Reporter: fzh2003(a)yeah.net CC: dimesio(a)earthlink.net, michael(a)fds-team.de, sebastian(a)fds-team.de Created attachment 65029 --> https://bugs.winehq.org/attachment.cgi?id=65029 screenshot Android 9 kernel 4.9.154 model Huawei SEA-AL00 -- 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 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