December 2024 - Wine-Bugs - list.winehq.org

[Bug 56531] Final Fantasy XI Online: Some textures are transparent, malformed, or misplaced.

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=56531 --- Comment #5 from Chiitoo <chiitoo(a)gentoo.org> --- Yeah, I still want to get the trace sorted and all. Maybe it would still be interesting to see what was happening actually. -- 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.

Dec. 31, 2024

[Bug 57608] Automatically end all processes after a wineserver crash.

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57608 Zeb Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12(a)gmail.com --- Comment #1 from Zeb Figura <z.figura12(a)gmail.com> --- (In reply to Bernhard Übelacker from comment #0) > If a wineserver crash happens all other processes stay hanging in the system. > > These processes may have still windows open, > which no longer react to user input. > And may hold resources until the user reboots or kills the processes. > > Would it be possible for them to just end too, > when the connection to wineserver disappears? How? What's going to kill them? -- 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.

Dec. 31, 2024

[Bug 56531] Final Fantasy XI Online: Some textures are transparent, malformed, or misplaced.

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=56531 --- Comment #4 from Zeb Figura <z.figura12(a)gmail.com> --- Huh, okay, no idea what went wrong, and I didn't get around to debugging it yet, but seems plausible enough that I fixed my own error there :-) -- 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.

Dec. 31, 2024

[Bug 57621] New: using glfw with angle doesn't seem to work

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57621 Bug ID: 57621 Summary: using glfw with angle doesn't seem to work Product: Wine Version: 9.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: juan3(a)yandex.com Distribution: --- Created attachment 77741 --> https://bugs.winehq.org/attachment.cgi?id=77741 Wine crashes trying to run red_circle, something to do with not finding symbols on the dlls when building this project under msys2 windows https://github.com/Kreijstal/glfw-example.git and running it under wine, with the non windows dll dependencies copied over. It turns it can't run under wine. It works fine under windows however. -- 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.

Dec. 31, 2024

[Bug 17930] Cygwin compilation breaks without --disable-16bit

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=17930 Gabriel Ravier <gabravier(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gabravier(a)gmail.com -- 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.

Dec. 31, 2024

[Bug 57600] Application not showing console output

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57600 --- Comment #2 from Angel <angel.narvaez(a)civiceye.com> --- 1. When opening the app in windows from cmd.exe, cmd.exe spawns a new console window where the app/log is showing 2. Yes. I did try wine <app> | cat. I'm attaching a couple of screenshots (one of the app running under windows, and one of the app running under wine). I think you are correct in that wine9 seems to match the Windows behavior closer than wine8 for console inheritance since both platforms create a new windows console window. I just seems odd that wine <app> | cat doesn't produce the console output. One thing I had tried when I filed a ticket in crossover is this: ----------------- I downloaded the source to my machine and reverted the changes to dlls/ntdll/unix/env.c in the commit (https://gitlab.winehq.org/wine/wine/-/commit/4b63e888945b8ada2ddc043e435b93…) After recompiling and running with "wine app | cat" the unix console does show the output as expected. ----------------- Not sure if this change would affect console inheritance behavior or not but it does produce the desired 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.

Dec. 31, 2024

[Bug 57620] High CPU load when setting "Screen resolution" to other value then 96

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57620 Ulrich Gemkow <ulrich.gemkow(a)ikr.uni-stuttgart.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Regression SHA1| |0f1d999bb878ea54214057d3662 | |c116271ec4812 Keywords| |regression -- 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.

Dec. 31, 2024

[Bug 57620] New: High CPU load when setting "Screen resolution" to other value then 96

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57620 Bug ID: 57620 Summary: High CPU load when setting "Screen resolution" to other value then 96 Product: Wine Version: 10.0-rc3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: ulrich.gemkow(a)ikr.uni-stuttgart.de Distribution: --- I am seeing a high CPU load (more than 40%) for the application and the Xorg server (also more than 40%) when setting the screen resolution with winecfg to (i.e) 192. Also the window manager shows a high load. With screen resolution 96 the high load does not happen. The application is Framemaker 8 and the Desktop Environment is somewhat special (Trinity desktop, a KDE 3.5 derivate) A bisect shows the following commit 0f1d999bb878ea54214057d3662c116271ec4812 is the first bad commit commit 0f1d999bb878ea54214057d3662c116271ec4812 Author: Rémi Bernon <rbernon(a)codeweavers.com> Date: Tue Nov 19 13:28:39 2024 +0100 winex11: Update the Win32 window state outside of event handlers. I am grateful for any advice on what further information can help to solve this problem. -- 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.

Dec. 31, 2024

[Bug 56886] Wincatalog can't scan folders

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=56886 --- Comment #7 from Sven Baars <sven.wine(a)gmail.com> --- I still haven't figured out the exact implementation, but I found at least one issue with the current implementation. if (CreateProcessA( "C:\\windows\\syswow64\\msinfo32.exe", NULL, NULL, NULL, FALSE, 0, NULL, NULL, &si, &pi )) { [get the env from pi] query_env_var(env, L"PROCESSOR_ARCHITECTURE", is_win64 ? L"AMD64" : L"x86"); query_env_var(env, L"PROCESSOR_ARCHITEW6432", is_win64 ? NULL : L"AMD64"); } The above test works for me on windows but fails for me on wine. The exact issue with this application is a bit different, but it's similar in the sense that the native machine is not reported where it should be. Putting back the old code, but replacing RtlInitUnicodeString( &nameW, L"x86" ); RtlSetEnvironmentVariable( env, &arch_strW, &nameW ); with RtlSetEnvironmentVariable( env, &arch_strW, get_machine_name( machine, &nameW )); fixes the application and the above test. -- 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.

Dec. 31, 2024

[Bug 57618] Using MaxQDA 24 is impossible, because test license code is not accepted

by WineHQ Bugzilla

https://bugs.winehq.org/show_bug.cgi?id=57618 --- Comment #6 from Rafał Mużyło <galtgendo(a)o2.pl> --- (In reply to Louis Lenders from comment #3) ...Kerberos support might be a problem, but rarely ever is.. -- 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.

Dec. 31, 2024