- Wine-Bugs - list.winehq.org

[Bug 56499] New: Ragnarok Origin launcher: freezing with wined3d.
by WineHQ Bugzilla March 31, 2024

March 31, 2024

https://bugs.winehq.org/show_bug.cgi?id=56499 Bug ID: 56499 Summary: Ragnarok Origin launcher: freezing with wined3d. Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: manoelricado(a)outlook.com Distribution: --- The Ragnarok Origin launcher is experiencing freezing issues when using wined3d. whereas it operates without any freezing problems when utilizing dxvk. -- 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 5

[Bug 56502] New: Mouse gets stuck in one direction while playing some games
by WineHQ Bugzilla March 31, 2024

March 31, 2024

https://bugs.winehq.org/show_bug.cgi?id=56502 Bug ID: 56502 Summary: Mouse gets stuck in one direction while playing some games Product: Wine Version: 9.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: PedroCarn(a)gmail.com Distribution: --- I noticed that on some Fullscreen games my mouse gets stuck around 20% of the screen, feels like I hit a invisible wall - vertically - Monitor 1 and horizontally - Monitor 2 *if I change the game to Monitor 2*, there was always one direction I couldn't move. My monitor setup: Monitors: 2 0: +*DP-1 2560/600x1440/340+1920+0 DP-1 1: +DP-2 1920/600x1080/340+0+0 DP-2 I noticed this issue on the following games: - Overwatch 2 - Horizon Zero Dawn - Ghost Recon Breakpoint System: OS: Arch Linux KERNEL: 6.8.2-zen2-1-zen CPU: AMD Ryzen 7 5800X3D 8-Core GPU: AMD Radeon RX 6800 XT (radeonsi, navi21, LLVM 17.0.6, DRM 3.57, 6.8.2-zen2-1-zen) GPU DRIVER: 4.6 Mesa 24.0.3-arch1.2 DE: Gnome 46 [Wayland] WM: Mutter RAM: 32 GB Wine Version 9.0 This only happened after updating from Gnome 45 to Gnome 46, I have been testing different wine/proton versions and always had the same problem and was driven me insane until I found a few workarounds: 1 - Disable one of the monitors 2 - Change the render to Xorg. 3 - Setting both monitors to the same resolution 1920x1080. 4 - In winecfg unchecking "Allow the window manager to control the windows" seems to fix the issue. It's possible that it might be a mutter/gnome bug but since I am only experienced this while gaming using wine, I decided to open the bug here. -- 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 1

[Bug 34883] New: Warface gface version does not start
by wine-bugs＠winehq.org March 29, 2024

March 29, 2024

http://bugs.winehq.org/show_bug.cgi?id=34883 Bug #: 34883 Summary: Warface gface version does not start Product: Wine Version: 1.7.4 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: levanchelidze(a)gmail.com Classification: Unclassified Created attachment 46489 --> http://bugs.winehq.org/attachment.cgi?id=46489 Terminal output I created a 32 bit wine prefix and installed firefox 25 windows version on it then I installed warface plugin from gface and installed the game without a problem but when I try to start the game it shows a black screen and then disables it and just shows the webpage I was on http://i.imgur.com/3JT0ZUO.png -- 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 5

[Bug 5129] Faststone Image Viewer doesn't show all images when scrolling
by WineHQ Bugzilla March 29, 2024

March 29, 2024

https://bugs.winehq.org/show_bug.cgi?id=5129 --- Comment #40 from unxed <unxed(a)mail.ru> --- Wrote a script implementing workaround from comment 23. This will clear you Wine prefix and install fresh working FastStone 5.6 curl -sSL https://raw.githubusercontent.com/unxed/fswine/main/fswine.sh > /tmp/fswine.sh && bash /tmp/fswine.sh Even with HiDPI support! Don't forget to set you screen resolution to something like 200 in winecfg. Tested on Linux Mint 21.3 Virginia, Cinnamon, amd64 wine-6.0.3 (Ubuntu 6.0.3~repack-1) Source code: https://github.com/unxed/fswine/blob/main/fswine.sh -- 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 0

[Bug 5129] Faststone Image Viewer doesn't show all images when scrolling
by WineHQ Bugzilla March 29, 2024

March 29, 2024

https://bugs.winehq.org/show_bug.cgi?id=5129 --- Comment #39 from unxed <unxed(a)mail.ru> --- oh, it was a mistake. a but still persist even with small thumbnail sizes. -- 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 0

[Bug 5129] Faststone Image Viewer doesn't show all images when scrolling
by WineHQ Bugzilla March 29, 2024

March 29, 2024

https://bugs.winehq.org/show_bug.cgi?id=5129 --- Comment #38 from unxed <unxed(a)mail.ru> --- Workaround for HiDPI screens: 1. Set screen resolution to 200 DPI in winecfg 2. Set minimal thumbnail size in Faststone voila, bug is gone! works at least at 3072 x 1728 -- 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 0

[Bug 5129] Faststone Image Viewer doesn't show all images when scrolling
by WineHQ Bugzilla March 29, 2024

March 29, 2024

https://bugs.winehq.org/show_bug.cgi?id=5129 --- Comment #37 from unxed <unxed(a)mail.ru> --- Tested with 3072 x 1728 screen size. If I set screen resolution in Wine to 167 dpi or less, bug stops reproducing. If I set it to 168 dpi or more, it starts reproducing again. Faststone 5.6 wine-6.0.3 (Ubuntu 6.0.3~repack-1) -- 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 0

[Bug 32816] New: Enemies are not displayed in Chompston
by wine-bugs＠winehq.org March 29, 2024

March 29, 2024

http://bugs.winehq.org/show_bug.cgi?id=32816 Bug #: 32816 Summary: Enemies are not displayed in Chompston Product: Wine Version: 1.5.22 Platform: x86-64 URL: http://www.contralogic.com/games/chompston/ OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: vulture6(a)mail.com Classification: Unclassified The enemies (which should be translucent) are not displayed, making the game impossible to play. The console is full of 'fixme:d3d:gl_blend_factor Unhandled blend factor 0.' messages. Download from: http://www.contralogic.com/games/chompston/ System: GTS 250 with Nvidia driver version 313.09 -- 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 4836] Page Maker 6.5 / 7.0 page fault when printing graphics
by WineHQ Bugzilla March 28, 2024

March 28, 2024

https://bugs.winehq.org/show_bug.cgi?id=4836 Aida Jonikienė <aidas957(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aidas957(a)gmail.com --- Comment #33 from Aida Jonikienė <aidas957(a)gmail.com> --- Does this issue still exist on Wine 9.5? -- 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 0

[Bug 56488] New: TCP socket appears to be in use but it is not
by WineHQ Bugzilla March 28, 2024

March 28, 2024

https://bugs.winehq.org/show_bug.cgi?id=56488 Bug ID: 56488 Summary: TCP socket appears to be in use but it is not Product: Wine Version: 4.0-rc2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: bugzilla400(a)gmail.com Distribution: --- I have a .net 3.5 application that runs fine on Windows but have a problem when running on Debian. The problem is a socket binding error "address already in use". CODE: System.Net.Sockets.SocketException: Unknown error (0x2740) at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress) at System.Net.Sockets.Socket.Bind(EndPoint localEP) netstat and lsof commands don't show the socket that appears to be in use, so I assume it's not really in use. Furthermore the problem only happens, and it always happen, in the following circumstance. 1. The program A.exe listens successfully on the server socket <anyip>:<port>. 2. Then it start the program B.exe and close itself (closing the socket too). 3. Program B.exe do something and then starts again A.exe. 4. A.exe try to bind the server socket but in that case it fails with the error "address already in use". 5. Restart A.exe, now the binding success. To start the new process I'm using System.Diagnostic.Process. CODE: // This is only a generic example var process = new Process() { StartInfo = new ProcessStartInfo { FileName = "cmd", Arguments = "/c /usr/bin/bash -c \"/usr/bin/sleep 5 && /usr/bin/wine path/of/process/program.exe\"", UseShellExecute = false, WorkingDirectory = "the/working/dir", } } These are the socket states after each steps (netstat): 1. LISTEN 2. not listed due to socket is closed 3. not listed due to socket is closed 4. not listed due to socket is closed <- But I have got the error 5. LISTEN I suppose that the A and B processes close properly because I don't see them in htop anymore. There seems to be something left hanging. I've found that if I don't relaunch A.exe from B, but do it manually, everything works fine. I also noticed this behavior that I wasn't expecting: - if I use socket.Accept the socket is bound to the A.exe process, - if I use socket.BeginAccept the socket is bound to the winserver32 process Clearly if I simply close the A.exe application and restart it all works fine. -- 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 1