February 2021 - Wine-bugs - list.winehq.org

[Bug 40838] New: I am able to install the Launcher. however as soon as installation/ updates are complete, the window crashes into a small box at the upper right corner of my screen , then crashes comepletely after that
by wine-bugs＠winehq.org 19 Apr '23

19 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=40838 Bug ID: 40838 Summary: I am able to install the Launcher. however as soon as installation/updates are complete, the window crashes into a small box at the upper right corner of my screen, then crashes comepletely after that Product: Wine Version: 1.9.11 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ak11(a)cox.net Distribution: --- Created attachment 54811 --> https://bugs.winehq.org/attachment.cgi?id=54811 NO THIS IS NOT THE SAME CASE AS bug 40628....the logs are different I am able to install the Launcher. however as soon as installation/updates are complete, the window crashes into a small box at the upper right corner of my screen, then crashes comepletely after that. Any ideas? I hope its an easy fix, i almost have it working! -- 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 40

[Bug 44211] New: Wine (2.21) doesn't work anymore on any game on FreeBSD
by wine-bugs＠winehq.org 19 Apr '23

19 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=44211 Bug ID: 44211 Summary: Wine (2.21) doesn't work anymore on any game on FreeBSD Product: Wine Version: 2.21 Hardware: x86-64 OS: FreeBSD Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: adrien_fernandes2(a)hotmail.com Created attachment 59990 --> https://bugs.winehq.org/attachment.cgi?id=59990 Output of AC with csmt FreeBSD/amd64 11.1 (the release version in december 2017) Wine staging 2.21 32 bits (built from a 32 bits chroot) nVidia 765m (nvidia-driver-384.59) 12 GB RAM (even if 32 bits applications take less, you have the information) from my 32 bits chroot, I installed the nVidia driver libGL.so -> libGL-NVIDIA.so.1 libGL.so.1 -> libGL-NVIDIA.so.1 libGLESv2.so -> libGLESv2-NVIDIA.so.2 libGLESv2.so.2 -> libGLESv2-NVIDIA.so.2 It always worked that way four months ago (last time I was on my computer) So actually I tried Streets of Rogue and Assassin's Creed. I copy the output of AC so you can see what the terminal says me. I set CSMT on one try and disabled it on the second. (Assassin's Creed always worked in the past, that's why I give you its output) -- 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 12

[Bug 35234] New: Fallout: New Vegas launcher crashes when selecting a DLC by double click
by wine-bugs＠winehq.org 19 Apr '23

19 Apr '23

http://bugs.winehq.org/show_bug.cgi?id=35234 Bug ID: 35234 Summary: Fallout: New Vegas launcher crashes when selecting a DLC by double click Product: Wine Version: 1.7.9 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: gyebro69(a)gmail.com Classification: Unclassified Created attachment 46995 --> http://bugs.winehq.org/attachment.cgi?id=46995 terminal output I browsed Bugzilla's already closed and currently opened bug reports related to Fallout: New Vegas/Fallout 3, but haven't find anything similar to this. It's not a new bug because I can reproduce it with Wine 1.4.1, 1.6.1, 1.7.9 as well. The problem: when you start Fallout:New Vegas, the launcher offers an option named <Data Files> where you can enable/disable the installed DLCs. If I double-click on the name of the DLC, Wine produces a crash as can be seen in the attached log. Single clicking on the name of the DLC doesn't produce the crash. This was tested with a clean wineprefix, without any dll overrides, dwrite and gameoverlayrenderer already disabled. Fedora 19 x86 X.Org X Server 1.14.4 Nvidia binary drivers 325.15 -- 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 50601] New: gave this error when running application with wine
by WineHQ Bugzilla 19 Apr '23

19 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=50601 Bug ID: 50601 Summary: gave this error when running application with wine Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: benjaminlihao(a)gmail.com Distribution: --- Created attachment 69289 --> https://bugs.winehq.org/attachment.cgi?id=69289 backtrace error I basically used the wine to open an application but when I opened it, the application crashed and gave me an error. -- 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.

1 4

[Bug 45575] New: Skyrim: No controller input when multiple controllers are connected
by wine-bugs＠winehq.org 19 Apr '23

19 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=45575 Bug ID: 45575 Summary: Skyrim: No controller input when multiple controllers are connected Product: Wine Version: 3.13 Hardware: x86-64 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ahyattdev(a)icloud.com Skyrim works fine when I have one wired Xbox 360 controller plugged in but when I have another one also plugged into my machine that I am not using neither controller works with the game. I have tested what the behavior is on Windows and Skyrim works fine when multiple Xbox controllers are connected. When running through Wine none of the controllers give any input. -- 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 2

[Bug 48582] New: PlayStation Now: Controllers aren't detected with Microsoft's native xinput1_3.dll
by WineHQ Bugzilla 19 Apr '23

19 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=48582 Bug ID: 48582 Summary: PlayStation Now: Controllers aren't detected with Microsoft's native xinput1_3.dll Product: Wine Version: 5.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: xinput Assignee: wine-bugs(a)winehq.org Reporter: devilj(a)outlook.pt Distribution: --- Xbox One controllers (at least) aren't detected when using Microsoft's native xinput1_3.dll, but they are working fine when using Wine's built-in version. I captured a log using Wine's BUILT-IN implementation, but it doesn't say much. The program polls "XInputGetStateEx" to get the state of indices 0 and 1: 004d:trace:xinput:XInputGetStateEx (index 0, state 0842FEB0)! 004d:trace:xinput:XInputGetStateEx (index 1, state 0842FEB0)! And the respective +relay (using only the built-in module): 0040:Call xinput1_3.XInputGetStateEx(00000000,07edfeb0) ret=0048d99d 0040:Ret xinput1_3.XInputGetStateEx() retval=00000000 ret=0048d99d 0040:Call xinput1_3.XInputGetStateEx(00000001,07edfeb0) ret=0048d99d 0040:Ret xinput1_3.XInputGetStateEx() retval=0000048f ret=0048d99d -- 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.

1 3

[Bug 46151] New: XInput support doesn't support rumble on the DS4 ( at least)
by wine-bugs＠winehq.org 19 Apr '23

19 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=46151 Bug ID: 46151 Summary: XInput support doesn't support rumble on the DS4 (at least) Product: Wine Version: unspecified Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: xinput Assignee: wine-bugs(a)winehq.org Reporter: epigramx(a)yahoo.com Distribution: --- That would be a neat feature and it's lacking right now. All Xbox Controllers support two motors on the device. It appears that currently Wine doesn't provide that data to applications. I was interested in the DS4 specifically out of the box but I support the feature may be missing on the actual Xbox controllers as well. -- 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 45688] New: Gamepad appears both as dinput and xinput ( eg. Valkyria Chronicles)
by wine-bugs＠winehq.org 19 Apr '23

19 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=45688 Bug ID: 45688 Summary: Gamepad appears both as dinput and xinput (eg. Valkyria Chronicles) Product: Wine Version: 3.11 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-dinput Assignee: wine-bugs(a)winehq.org Reporter: gabriel.corona(a)enst-bretagne.fr Distribution: --- AFAIU, on Windows a gamepad appears either on DirectInput or on XInput. Some games are helpful and automatically work with both. For example, Valkyria Chronicles apparently automatically switches between DirectInput and Xinput based on the latests input. On Wine >= 3.3, every gamepad appears both on DirecrInput and XInput. This is useful because the gamepad can work both on DirectInput and XInput gamed. However, on Valkyria Chronicles (for example) the effect is that the game switches randomly between the two modes because it apparently sees the same gamepad from both APIs. This can be seen because the buttons displayes on screen change from numbered key labels ("1", "2", "3", etc.) and XInput based key labels ("A", "B", "C", "D"). In order to sucessfully run the game, I has to disable the gamepad from DirectInput (using "wine control"). This works, but prevents running DirectInput only games without reconfiguration. A possible workaround would be to have an option to disable DirectInput gamepads if both libraries are mapped in the same process. -- 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 44086] New: HiDPI: Consider evaluating `GDK_SCALE` for default DPI size
by wine-bugs＠winehq.org 19 Apr '23

19 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=44086 Bug ID: 44086 Summary: HiDPI: Consider evaluating `GDK_SCALE` for default DPI size Product: Wine Version: 2.0.3 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: pmenzel+bugs.winehq.org(a)molgen.mpg.de Distribution: --- Opening the Wine configuration on a HiDPI monitor, the fonts are very small. Despite having the user to increase the DPI size under the tab *Graphics*, environment variables like `GDK_SCALE` [1] should be evaluated, and the default DPI number be adjusted accordingly. [1] https://wiki.archlinux.org/index.php/HiDPI -- 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 2

[Bug 38749] New: Left 4 Dead: text in terminal is unreadable
by wine-bugs＠winehq.org 19 Apr '23

19 Apr '23

https://bugs.winehq.org/show_bug.cgi?id=38749 Bug ID: 38749 Summary: Left 4 Dead: text in terminal is unreadable Product: Wine Version: 1.7.44 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: trivial Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ilya-valeev(a)yandex.ru Distribution: --- Created attachment 51666 --> https://bugs.winehq.org/attachment.cgi?id=51666 Log When I call terminal (`), I cant read some text (see screenshot). Font tips from here: https://appdb.winehq.org/objectManager.php?sClass=version&iId=19444 doesnt help. Tried wine 1.6.2, 1.7.42 and 1.7.44. Debian 8. 1920x1080 -- 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